Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 3549 invoked from network); 5 Nov 2007 09:24:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Nov 2007 09:24:56 -0000 Received: (qmail 73738 invoked by uid 500); 5 Nov 2007 09:24:44 -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 73727 invoked by uid 99); 5 Nov 2007 09:24:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2007 01:24:44 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joerg.von.frantzius@artnology.com designates 80.67.18.15 as permitted sender) Received: from [80.67.18.15] (HELO smtprelay03.ispgateway.de) (80.67.18.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2007 09:25:10 +0000 Received: (qmail 12923 invoked from network); 5 Nov 2007 09:24:22 -0000 Received: from unknown (HELO [192.168.100.11]) (383542@[195.143.217.178]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP; 5 Nov 2007 09:24:22 -0000 Message-ID: <472EE257.4060409@artnology.com> Date: Mon, 05 Nov 2007 10:28:55 +0100 From: Joerg von Frantzius User-Agent: Thunderbird 2.0.0.6 (X11/20070801) MIME-Version: 1.0 To: jdo-dev@db.apache.org CC: jdo-experts-ext@sun.com Subject: Re: multiple databases one PM/TX References: <4463CFBC.2050403@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> <472129C7.9050 505@sun.com> <1193406556.4721f05c08bab@webmail.jpox.o rg> In-Reply-To: <1193406556.4721f05c08bab@webmail.jpox.org> X-Enigmail-Version: 0.95.3 Content-Type: multipart/mixed; boundary="------------040403080809050406020702" X-Virus-Checked: Checked by ClamAV on apache.org --------------040403080809050406020702 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Erik, there is one thing that I don't understand about this proposed feature (which may be just me not seeing the obvious point of course :) Running 2PC on multiple data sources is handled already by J2EE implementations, and, as far as I recall, there are also libraries available that provide a JTA without a full blown J2EE server. Why would you want to duplicate this already existing and available functionality in JDO? Regards, Jörg Erik Bengtson schrieb: > 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. > > 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: > > /jdoconfig/ sequence unbounded PMF > /jdoconfig/ sequence unbounded Resource > > /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 > > 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: > > 1 - CredentialMapping - the CredentialMapping takes the principal of the running > application and sets it as client id - eg. ConnectionClientID=CredentialMapping > 2 - Identity – the client id is taken from the id right after the Identity word > - eg. ConnectionClientID=Identity:MyUser > > ReadOnly > ---------------------------- > ReadOnly (accepts true, false) will block write operations to this connection > > TwoPhaseCommit > -------------------------- > Two options: > > 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 > > Example: > > > > > > > > > > > > > > > > connection-client-id=”CredentialMapping”/> > > > > > > > > > > > > > > > > > > > > > > > > > > Quoting Michelle Caisse : > > >> Hi, >> >> We will have our regular meeting Friday, October 26 at 9 am PDT to >> discuss JDO TCK issues and status. >> >> Dial-in numbers are: >> 866 230-6968 294-0479# >> International: +1 865 544-7856 >> >> Agenda: >> >> 1. Subquery spec update >> 2. Other issues >> >> Action Items from weeks past: >> >> [Oct 12 2007] AI Michael take a look at subquery tck tests. >> https://issues.apache.org/jira/browse/JDO-446 >> >> [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml. >> >> [June 22 2007] AI Craig discuss svn:eol-style on email. >> >> [June 22 2007] AI Craig write a proposal on annotation overrides for >> the expert group. >> >> [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. >> >> [May 25 2007] AI Matthew Adams prepare a proposal with just the basics >> of schema synchronization with jdo and orm metadata. >> >> [May 18 2007] AI Craig update http://wiki.apache.org/jdo/ >> CurrentDevelopment wiki page >> >> [Apr 27 2007] AI Craig review Query API and send email to experts. >> >> [Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and >> attach his discussion document to it. >> >> [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.. >> >> [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. >> >> [Aug 11 2006] AI Craig propose some semantics for behavior if user >> tries to add to a list where the ordering element is incorrect. >> >> [Jul 14 2006] AI: Erik document 220 annotations that don't have a >> corresponding JDO concept. >> >> [Jun 23 2006] AI Martin look at what Hibernate and TopLink support >> for Enum types. In progress. >> >> [Apr 14 2006] AI Craig: update the roadmap for JDO. In progress. >> >> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5 >> issues. In progress >> >> [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. >> >> -- Michelle >> >> > > > > > > --------------040403080809050406020702--