Don't use the dummy transaction manager. This tries to bind to JNDI and fails.
Use the GenericTransactionManagerLookup instead, which should detect the WebLogic transaction manager.
Thanks. That helped.
I am relatively new to the JBoss cache world and since i am porting this code over from running within JBoss to WLS, i am not sure what all in the code belongs to the JBoss cache vs JBoss AS.
In my application code, the JNDI lookup is done using the MBeanServerLocator class as shown here:
MBeanServer server = MBeanServerLocator.locate();
cache = (TreeCacheMBean)MBeanProxyExt.create(TreeCacheMBean.class,"jboss.cache:service=TreeCache", server);
The cache is then manipulated using cache.put() and cache.get() methods.
I am assuming the TreeCache is registered into the JBoss AS JNDI automatically by the JBoss AS framework using the "replySync-service.xml" configuration file.
In the sample that u have put out, if i understand it right, the job of registering the TreeCache is being done by the JBossCacheManager class.
Was wondering if it was possible to use the MBeanServerLocator within WebLogic server to locate the JBoss cache ? Or would I need to use the JBossCacheManager approach to register the TreeCache?
Even in JBoss AS you shouldn't be using the DummyTransactionManager. The GenericTransactionManagerLookup would locate the JBossTransactionManager, which comes with JBoss AS.
There is no such thing as a JBossCacheManager. What I was talking about was a JTA compliant TransactionManager.
To bind JBC to JNDI use a startup class which instantiates and binds a JBoss Cache instance. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAndWebLogic - the example is for WLS 8.1, but I'm sure the concepts apply to WLS 10 as well.
Was able to deploy the example from http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAndWebLogic -
This helped me register the JBoss cache in WLS' JNDI tree and use the cache from my app.