Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: unknown (nike.apache.org: error in processing during lookup of
 myawn@ebay.com)
DomainKey-Signature: s=corp; d=ebay.com; c=nofws; q=dns;
  h=X-EBay-Corp:X-IronPort-AV:Received:Received:X-MimeOLE:
   Content-class:MIME-Version:Content-Type:Subject:Date:
   Message-ID:X-MS-Has-Attach:X-MS-TNEF-Correlator:
   Thread-Topic:Thread-Index:From:To:Return-Path:
   X-OriginalArrivalTime;
  b=U0n/MC88b9ksyPS1hEBr7uSqF0Sj8p7b872+BWK7cuUOlynKDqcr7MVH
   QM51+WTx+vQyJnVqHc+8j2NyqFXcE0h3L59+kqhJtyaLBcXQQtAk7A6j/
   JnBWQCWy7w203Ul;
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CA0ED0.4D474C72"
Subject: Architectural overview (how to get started targeting a new
 persistence back-end) ? 
Date: Mon, 27 Jul 2009 08:38:36 -0700
Message-ID: 
 <2EFDE7AD867BF346BA5130160871B9920CBE37F3@RHV-EXM-03.corp.ebay.com>
Thread-Topic: Architectural overview (how to get started targeting a new
 persistence back-end) ? 
Thread-Index: AcoO0E5WMNTUYr4kRneoILm4Zf8yFA==
From: "Yawn, Mike" <myawn@ebay.com>
To: <dev@openjpa.apache.org>

------_=_NextPart_001_01CA0ED0.4D474C72
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm curious as to whether there are any presentations or other =
architectural-level overviews that aren't readily apparent from browsing =
the OpenJPA site.   In particular, I'm looking to get a better =
high-level understanding of the OpenJPA architecture, in order to be =
able to scope out what sort of effort would be involved in plugging a =
new provider into OpenJPA.

=20

Areas where I think I'd need to extend what is currently there include:

-          subclassing the Entity parsing code to support additional =
annotations that we've added beyond the JPA standard

-          subclassing the data model classes to add attributes =
corresponding to the additional annotations

-          implementing our own EntityManager to be a fa=E7ade to our =
existing data layer back end

=20

But I suspect I've only scratched the surface of what would actually be =
needed, so I'm wondering if there is some sort of a general overview of =
the roles & responsibilities of a persistence provider in an OpenJPA =
implementation, that I could use as a checklist for scoping everything =
we would need to provide.

=20

=20

Thanks for any pointers / references.

=20

Mike Yawn

eBay Inc.


------_=_NextPart_001_01CA0ED0.4D474C72--