Hi Dominique,

that's exactly what I expected as well - however if I execute the code as is (i.e. without the surrounding XA stuff), I get an exception that tells me that no transaction has been started (STATUS_NO_TRANSACTION) - my exception is very similar to what has been reported at http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/200702.mbox/[EMAIL PROTECTED]

Therefore I tried to start the transaction myself ...

... any further help/guidance/hints is/are highly appreciated ...


kind regards,
Markus

-------- Original-Nachricht --------
Betreff:        Re: JBoss and Jackrabbit JCA
Datum:  Mon, 6 Aug 2007 16:25:01 +0200
Von:    Dominique Pfister <[EMAIL PROTECTED]>
Antwort an:     [email protected]
An:     [email protected]
Referenzen:     <[EMAIL PROTECTED]>



Hi Markus,

Apparently, your session is already associated with a transaction. I
don't unterstand why you'd want to access the XAResource directly in
your client code. I'd expect that if you left only your core code
(starting with the comment "// .... add new nodes & properties and
save them") JBoss would automatically execute the surrounding code you
inserted manually.

Kind regards
Dominique


On 8/6/07, Markus Reis <[EMAIL PROTECTED]> wrote:
Dear All,


I'm currently playing around with Jackrabbit's jca package and end up in
some strange errors (which will mainly be due to wrong use from my code
:-)). Here's my environment:
JBoss 4.0.5.GA
Java 1.5_06
Jackrabbit 1.3.1 (checked out and build tagged version)
jcr-ds.xml (only modified homeDir property - I experimented with both
true and false for bindSessionToTransaction):
   <connection-factories>
    <tx-connection-factory>
        <jndi-name>jcr/local</jndi-name>
        <xa-transaction/>
        <rar-name>jackrabbit-jca-1.3.1.rar</rar-name>
        <connection-definition>javax.jcr.Repository</connection-definition>
        <config-property name="homeDir"
type="java.lang.String">${jboss.server.data.dir}${/}jackrabbit</config-property>
        <config-property name="configFile"
type="java.lang.String">classpath:repository.xml</config-property>
        <config-property name="bindSessionToTransaction"
type="java.lang.Boolean">false</config-property>
    </tx-connection-factory>
   </connection-factories>

Here's my client code:
    XAResource xares =
((JCASessionHandle)session).getManagedConnection().getXAResource();
//xares is either of type org.apache.jackrabbit.core.XASessionImpl (if
bindSessionToTransaction is set to false and
org.apache.jackrabbit.jca.TransactionBoundXAResource if set to true)
    // create dummy Xid
    Xid xid = new XidImpl(counter++); //XidImpl is simply copied from
org.apache.jackrabbit.core.UserTransactionImpl
    ((org.apache.jackrabbit.core.XASessionImpl)xares).associate(null);
//I think I shouldn't do that :-)
    xares.start(xid, XAResource.TMNOFLAGS);

           // .... add new nodes & properties and save them
            Node root = session.getRootNode();
            Node child = root.hasNode(path.getRelativePath()) ?
root.getNode(path.getRelativePath()) : createFilePath(root,
path.getPathParts(), path.getObjectName());
            FileTypeResolver ftr = FileTypeResolver.instantiate();
            child.setProperty("jcr:mimeType", ftr.getMIMEType(obj));
            child.setProperty("jcr:data", new FileInputStream(obj));
            Calendar rightNow = Calendar.getInstance();
            child.setProperty("jcr:lastModified", rightNow);
            //child.setProperty("original-file-name", obj.getName());
            session.save();

    xares.end(xid, XAResource.TMSUCCESS);
    xares.prepare(xid);
    xares.commit(xid, false);
If I set bindSessionToTransaction to false and disassociate the
XAResource from it's transaction (calling associate(null)), I can start
(and end and commit) the transaction successfully - I have however the
strong feeling that I shouldn't do that :-)
If I set bindSessionToTransaction to true (which would be the default)
or if I do not disassociate the XAResource from it's transaction then I
always get an exception thrown at XASessionImpl line 227 (remember that
I'm working on 1.3.1).

I never found out why the XAResource was associated with a transaction
although bindSessionToTransaction was set to false.

It would be great if someone could tell me what I'm doing wrong and/or
point me to sample code that should work in my environment and/or tell
me if she/he already did something similar successfully when deployed on
JBoss.


many thanks,
Markus



--
Mag. Markus Reis

Austrian Research Centers GmbH - ARC
Research Studios
Studio Digital Memory Engineering

Thurngasse 8/3/20, A-1090 Wien
Mobile: +43 664 825 1106
Tel.: +43-1-585 05 37 - 16
Fax: +43-1-585 37 41

<[EMAIL PROTECTED]>
http://www.arcs.ac.at/
http://www.researchstudio.at/
http://dme.researchstudio.at/

HG Wien – FN 115980i – ATU14703506

Reply via email to