Hi Giota,

On 6/15/06, Giota Karadimitriou <[EMAIL PROTECTED]> wrote:
Thanks, but the reason for me to use JCA in the first place was in order
to have container managed JTA transactions.

AFAIK  the JCA project will handle that, the underlying connection is
an internal resource and must not participate in JTA transactions.

I wanted a session bean to
call jackrabbit repository (wrapped as RAR) perform some operation and
when the EJB finishes, the container (application server) would commit
or rollback the transaction.


btw, take a look to the message I sent yesterday about some problems
in the jca connector.

br,
edgar


> -----Original Message-----
> From: Edgar Poce [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 15, 2006 4:37 PM
> To: [email protected]
> Subject: Re: question reagrding JNDI datasource
>
> Hi
>
> On 6/15/06, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > On 6/14/06, Giota Karadimitriou <[EMAIL PROTECTED]>
wrote:
> > > I would just like to report that it is not feasible to use
datasource
> > > with JCA and this because of line 339 in
DatabasePersistenceManager
> > > which performs an explicit con.commit();
> >
>
> have you tried to configure the datasource that uses jackrabbit's
> persistence manager to not take part of JTA transactions?
>
> In jboss you can configure it the datasource deployment descriptor
> with a tag called "no-tx-datasource". See
> http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources
>
> br,
> edgar
>
> > Could you file a Jira issue about this? I'm not sure if we can (or
> > should) fix this right away without having to refactor extensively
as
> > the current database pm treats the underlying database as an
internal
> > resource that is not part of a higher-level transaction. In any case
> > it would be good to have a persistent reminder about the issue, even
> > if we decide to resolve it as Won't fix.
> >
> > BR,
> >
> > Jukka Zitting
> >
> > --
> > Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
> > Software craftsmanship, JCR consulting, and Java development
> >


Reply via email to