RE: Transaction rollback problems because of incomplete orion-ejb.jar

[Ron van Pol]

Just looked at bug 512. The behavior is very similar to what I'm experiencing. On initial deployment the orion-ejb.jar file is copied to the deployment directory. THis is also ok in my case. Problems start arising similarly after redeployment of the ejb module. After this the orion-ejb.jar is incomplete, that is, ONLY my sessionbeans lack the specified location in resource-ref-mapping. My entitybeans are ok however. Modifying the orion-ejb.jar by hand after initial deployment seems to work but that is not a acceptable procedure.

 

Thanks,

Ron

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of elephantwalker
Sent: Sunday, July 08, 2001 8:29 PM
To: Orion-Interest
Subject: RE: Transaction rollback problems because of incomplete orion-ejb.jar

Ron,

 

Take a look at bug 512. Your orion-ejb-jar.xml is being overwritten with a double deployment of the application. Same thing happened to me. AFAIK, the only work around is to use version 1.5.1 or earlier.

 

I reproduced this bug with a modified atm application.

 

Regards,

 

the elephantwalker

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ron van Pol
Sent: Sunday, July 08, 2001 9:29 AM
To: Orion-Interest
Subject: Transaction rollback problems because of incomplete orion-ejb.jar

Hi,

 

I'm using orion 1.5.2 and I have the following problem: I have a session-bean that is accessing a datasource in transaction context. I have added an orion-ejb.jar in <deployment jar>/WEB-INF, containing a resource-ref-mapping pointing to the EJBDS for I want transaction support for this datasource.

 

<session-deployment ... >

  <resource-ref-mapping location="jdbc/myEJBDS" name="jdbc/myDS" />

</session-deployment>

 

After I deploy the application I can see in the deployment-directory that Orion only succesfully copies all setting form my orion-ejb.jar for the entity-beans but fails to copy the settings for my session beans. The resource-ref-mapping for the session beans lacks the location. 

 

<session-deployment ... >

  <resource-ref-mapping name="jdbc/myDS" />

</session-deployment>

 

As a consequence the datasource doesn't point to the EJBDS and therefore will not participate in a transaction, that is, transaction rollbacks do not affect the changes made through this datasource.

 

The datasources.xml file looks like this:

 

<data-sources>

  <data-source

    class="com.evermind.sql.DriverManagerDataSource"

    name="DS"

    location="jdbc/myDS"

    xa-location="jdbc/xa/myDS"

    ejb-location="jdbc/myEJBDS"

    connection-driver="com.sap.dbtech.jdbc.DriverSapDB"

    url="jdbc:sapdb:DS"

    username="DBA"

    password="DBA"

    inactivity-timeout="30"

    schema="../../config/database-schemas/sapdb.xml"

  />

</data-sources>

 

 

So, help!

 

Ron