Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 64475 invoked from network); 29 Oct 2007 17:06:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Oct 2007 17:06:01 -0000 Received: (qmail 18635 invoked by uid 500); 29 Oct 2007 17:05:49 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 18620 invoked by uid 99); 29 Oct 2007 17:05:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Oct 2007 10:05:48 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.240.242.88] (HELO xcalia-msx.xcalia.com) (62.240.242.88) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 29 Oct 2007 17:05:50 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C81A4D.E678E88F" Subject: RE: multiple databases one PM/TX Date: Mon, 29 Oct 2007 18:05:23 +0100 Message-ID: <345CC4DC7C636849B221B217D34C31197305B8@intranet.xcalia.net> In-Reply-To: <1193406556.4721f05c08bab@webmail.jpox.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: multiple databases one PM/TX Thread-Index: AcgX12BSvLqNVeZFTkeNFmwRydAEdgCdTWvQ References: <4463CFBC.2050403@sun.com> <45B95F3A.8090006@sun.com> <45CBC6A8.8030101@sun.com> <45D4E5E7.2050505@sun.com> <45DE3995.7070404@sun.com> <45E70D47.2040700@sun.com> <45F097C5.6020403@sun.com> <45F9D2EE.4070802@sun.com> <4603598C.8080205@sun.com> <460C4010.50209@sun.com> <46159A52.30506@sun.coom> <461EC15F.4070600@sun.ccom> <4627E706.6010105@sun.com> <463145A4.5080003@sun.com> <463A7B49.7000905@sun.com> <464CD0EB.5010101@sun.com> <46565157.4070804@sun.com> <465F4B00.9060906@sun.com> <4668D1DE.1080105@sun.com> <4671BA1B.7080600@sun.com> <467AFECA.6050104@sun.com> <468452A4.7080404@sun.com> <4696A846.1000707@sun.com> <469FFFEE.9030303@sun.com> <46AA0FE7.9060102@sun.com> <412A2419-D8FE-438F-A503-373D72DB3199@SUNN.com> <46C52BB6.5040305@sun.com> <46D76C3C.6020903@sun.com> <46E0C4C8.5050103@sun.com> <46E9CA09.1070408@sun.com> <46F33ED0.8050005@sun.com> <46FC1E63.2040605@sun.com> <4705534C.2040806@sun.com> <470EABD8.2010008@sun.com> <47180BB8.6030108@sun.com> <1193406556.47 21f05c08 bab@webmail.jpox.org> From: "Eric Samson" To: "Erik Bengtson" , , X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C81A4D.E678E88F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello Erik, =20 Once again you start an important topic here! :-) =20 We also are working on a multi-data sources PMF. =20 I think the name "resource" could be confusing (I tend to prefer "data = source"). =20 Maybe the data source properties should be defined elsewhere (as you can = have quite complex configurations when you want to access non-relational = data stores)? =20 Best Regards, ....: Eric Samson, Founder & CTO, Xcalia Service your Data! =20 -----Message d'origine----- De : Erik Bengtson [mailto:erik@jpox.org]=20 Envoy=E9 : vendredi 26 octobre 2007 15:49 =C0 : jdo-dev@db.apache.org; jdo-experts-ext@sun.com Objet : multiple databases one PM/TX =20 In JPOX we are implementing the access to multiple datastores within a = single PM/TX. If not too late, I'm wonder if you like to hear a proposal to standardize the configuration of the "jdoconfig" and jdo metadata to be = able to handle this scenario. It may sound overkill, but IMO is a major advance = over JPA. =20 To introduce the subject, the goal is to handle persistence in multiple databases (e.g. derby, oracle, DB4O, Versant, XML) within a single JDO transaction/ single PM. From the user point of view, there are two items = that must be configured, jdo metadata, jdo configuration, in which would be = part of this proposal, so I show below an example of the configurations: =20 /jdoconfig/ sequence unbounded PMF /jdoconfig/ sequence unbounded Resource =20 /PMF/ /PMF/@Class /PMF/@TransactionTimeout /PMF/@... /Resource/ /Resource/@Name /Resource/Connection Settings/ /Resource/Connection Settings/@ConnectionFactoryName /Resource/Connection Settings/@ConnectionClientID /Resource/Connection Settings/@ReadOnly /Resource/Connection Settings/@... /Resource/Transaction/ /Resource/Transaction/@TwoPhaseCommit /Resource/Transaction/@Timeout =20 ConnectionClientID ---------------------------- ConnectionClientID is the identifier for the connection. Some databases = such as Oracle use this to identify the end user (not the connection user). ConnectionClientID would accept the values: =20 1 - CredentialMapping - the CredentialMapping takes the principal of the = running application and sets it as client id - eg. = ConnectionClientID=3DCredentialMapping 2 - Identity - the client id is taken from the id right after the = Identity word - eg. ConnectionClientID=3DIdentity:MyUser =20 ReadOnly ---------------------------- ReadOnly (accepts true, false) will block write operations to this = connection =20 TwoPhaseCommit -------------------------- Two options: =20 1 - LastLoggingResource - If the resource is non XA, push down this = resource in commit order. 2 - Emulated - Emulates non XA protocol. Heuristics errors could happen =20 Example: =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 Quoting Michelle Caisse : =20 > Hi, >=20 > We will have our regular meeting Friday, October 26 at 9 am PDT to > discuss JDO TCK issues and status. >=20 > Dial-in numbers are: > 866 230-6968 294-0479# > International: +1 865 544-7856 >=20 > Agenda: >=20 > 1. Subquery spec update > 2. Other issues >=20 > Action Items from weeks past: >=20 > [Oct 12 2007] AI Michael take a look at subquery tck tests. > https://issues.apache.org/jira/browse/JDO-446 >=20 > [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml. >=20 > [June 22 2007] AI Craig discuss svn:eol-style on email. >=20 > [June 22 2007] AI Craig write a proposal on annotation overrides for > the expert group. >=20 > [May 25 2007] AI everyone Download the Grails demo from grails.org = and > check it out. Also look at Grails/Groovy ExpandoMetaClass that has = the > magic to avoid reflection and enhancement. >=20 > [May 25 2007] AI Matthew Adams prepare a proposal with just the = basics > of schema synchronization with jdo and orm metadata. >=20 > [May 18 2007] AI Craig update http://wiki.apache.org/jdo/ > CurrentDevelopment wiki page >=20 > [Apr 27 2007] AI Craig review Query API and send email to experts. >=20 > [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions = and > attach his discussion document to it. >=20 > [Mar 9 2007] AI Craig: Update the spec to require that the key of the > listener is the class name of the listener, for consistency with > proposed xml.. >=20 > [Mar 2 2007] AI Craig: update the JDOHelper class to include a string > constant "META-INF/jdo.xml" and a new method > getPersistenceManagerFactory taking no arguments. >=20 > [Aug 11 2006] AI Craig propose some semantics for behavior if user > tries to add to a list where the ordering element is incorrect. >=20 > [Jul 14 2006] AI: Erik document 220 annotations that don't have a > corresponding JDO concept. >=20 > [Jun 23 2006] AI Martin look at what Hibernate and TopLink support > for Enum types. In progress. >=20 > [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress. >=20 > [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK = 1.5 > issues. In progress >=20 > [Sep 2 2005] AI: To recruit members, update the web site. Articles on > TheServerSide directing attention to the site. T-shirts, logo. AI: > Craig write a ServerSide article. >=20 > -- Michelle >=20 > > >=20 =20 =20 =20 ------_=_NextPart_001_01C81A4D.E678E88F--