Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 45093 invoked from network); 6 Feb 2006 05:07:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Feb 2006 05:07:03 -0000 Received: (qmail 78664 invoked by uid 500); 6 Feb 2006 05:06:50 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 78603 invoked by uid 500); 6 Feb 2006 05:06:50 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 78591 invoked by uid 99); 6 Feb 2006 05:06:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Feb 2006 21:06:50 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com designates 66.249.82.203 as permitted sender) Received: from [66.249.82.203] (HELO xproxy.gmail.com) (66.249.82.203) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Feb 2006 21:06:49 -0800 Received: by xproxy.gmail.com with SMTP id t12so725458wxc for ; Sun, 05 Feb 2006 21:06:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=SnBg+d1hB5+m1dwuAc4XHcowHyOu6/yvWwCzGGR3IQioovHoN1yJ47uQq0ClOIX3erhzfP74X/bPBjFw8BnTuscNGrpwdNkMidJ8Nj6pT9ToTIyA8WHTyg5OIf4ZbZ5sRQVmQpgs7Gt7r8pWytlbpd64y57kqxSxTXVKJrELDRk= Received: by 10.70.38.11 with SMTP id l11mr3980414wxl; Sun, 05 Feb 2006 21:06:24 -0800 (PST) Received: from ?10.0.1.2? ( [67.180.143.96]) by mx.gmail.com with ESMTP id h14sm8577194wxd.2006.02.05.21.06.22; Sun, 05 Feb 2006 21:06:23 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <43E35E31.1020208@hogstrom.org> References: <3E5B32EC-F4EF-4F50-8FF1-47CE1DC39AA8@planet57.com> <7786EDD4-25BC-4D4F-99B0-31FF7A82468E@yahoo.com> <43E35E31.1020208@hogstrom.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5D0850EC-8A22-42FD-A330-8BC3974E3C37@planet57.com> Content-Transfer-Encoding: 7bit From: Jason Dillon Subject: Re: Oracle XA RAR for G1.0? Date: Sun, 5 Feb 2006 21:06:23 -0800 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.746.2) Sender: Jason Dillon X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Any clue on the required config to get the rar deployed? I'm trying to convert this URL to the params for the RAR: jdbc:oracle:thin:@mydbhost:1621:devdb Unfortunately the Oracle XA RAR does not take a URL, but wants granular configuration. Some obvious stuff I get (like the port number), but what to use for protocol and type, etc have me scratching my head. I also looked for the Javadocs for oracle.jdbc.xa.client.OracleXADataSource with no luck to see what properties it exposed. The only docs I can find are to expose the XAResource, but there must be more since the TranQL RAR is calling some of them. Any ideas? --jason On Feb 3, 2006, at 5:44 AM, Matt Hogstrom wrote: > I think David means that it has not been extensively tested and so > there are no gurantees that you'll simply be able to drop it in. > I'm currently working on a DB2 XA RAR and am still working out some > kinks. It should work well, we're just not sure its been testd > enough to know that it does. > > I looked on CodeHaus and it appears that Jeremy had not previous > released a SNAPSHOT. I compiled the connector this morning against > the Oracle 10.1.4.0 classes12.jar. > > I've published it and it is called tranql/rars/tranql-connector- > oracle-xa-1.0-SNAPSHOT.rar > > If someone can try this out then that would be excellent. I have > only compiled it and not tested it so caveat emptor. > > lichtner wrote: >> On Fri, 3 Feb 2006, David Jencks wrote: >>> It is likely to work if you build it. However I don't know that it >>> has been used in the last year or more, so I won't make any >>> promises. Matt might have tried it, I don't know. We have been a >>> bit reluctant to publish it without more evidence that it works >>> well. >> Why would it not work well? When I was in my last job I remember >> getting >> that rar to work with mysql xa, so it probably also works with >> Oracle xa.