Tejesh would you mind taking a look at castors implementations yourself
as I think this may be the fastest way to come to a solution. Under:
http://cvs.castor.codehaus.org/viewrep/castor/castor/trunk/src/main/java/org/castor/transactionmanager
you're able to take a look at current source. The JNDI implementation is:
JNDIENCTransactionManagerFactory.java
while for websphere51 you should take a look at:
WebSphere51TransactionManagerFactory.java
AbstractTransactionManagerFactory.java
According to the exception it seams to fail at getTransactionManager()
for websphere51. As class and method name have changed twice between 3
releases it may have changed again for websphere 6. Another option would
be that you need to configure at websphere that you need transactions.
Having said that I found a mail in archiv that states that websphere
does not support JNDI binding but I'm not sure if this was or is valid.
Sorry for not being able to offer more help but I don't see a chance to
reproduce that here.
Regards
Ralf
Tejesh Shetty schrieb:
Yes I did tried with 'websphere51' and I get the same exception
Nested error:
org.castor.transactionmanager.TransactionManagerAcquireException: Unable
to acquire instance of javax.transaction.TransactionManager: websphere51
I also have piece of code which looks up for Transaction Manager and the
class that I get back is
com.ibm.ejs.container.UserTransactionWrapper
I don't know if castor internally cast transaction manager to this class
incase of websphere51?
-----Original Message-----
From: Ralf Joachim [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 04, 2006 5:10 PM
To: [email protected]
Subject: Re: [castor-user] castor 1.0 with websphere 6.0
Hi Tejesh,
have you tried:
<transaction-demarcation mode="global">
<transaction-manager name="websphere51"/>
</transaction-demarcation>
Hopefully they didn't change classname and interface yet another time.
If you'd like to use JNDI you should check websphere manual about the
JNDI ENC the transaction manager is bound to. To identify the problem
you have it may help to take a look at the stacktrace and to know which
release of castor you are using.
If not already done you may want to take a look at:
http://castor.codehaus.org/database-conf.html#Transaction-demarcation
Regards
Ralf
Tejesh Shetty schrieb:
I am getting an exception when ejb tries to get transaction manager
for
websphere 6.0. We are doing one time initialization of JDOManager
during ejbCreate.
JDO config looks something like this..
<transaction-demarcation mode="global">
<transaction-manager name="jndi">
<param name="jndiEnc"
value="java:comp/UserTransaction"/>
</transaction-manager>
</transaction-demarcation>
Wondering if any one knows what config changes have to be done to get
right transaction manager.
Thanks.
**Tejesh Shetty | ****Software Developer, MortgageHub Inc. |
Conshohocken, PA | Tel: 610.834.3800 ext 106 | [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>m <mailto:[EMAIL PROTECTED]>**
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
