-
1. connection pooling in RC2?
thomas.diesler Dec 20, 2004 11:50 AM (in response to starksm64)I am trying to migrate from 3.0.0 to RC2 and see that there are some changes in database connection pooling. I was using ConnectionFactoryLoader in 3.0.0 and was handling transactions within the code itself.
Would someone give me an example of setting up the db2-service.xml file for the new corresponding connectoin manager I should use in Rc2?
Note, I did get the sample using LocalTXConnectionManager to work, but I get errors with the autocommit() in my code so I assume I need to use NoTXConnectionManager.
If this assumption is true, can someone give me a sample of NoTXConnectionManager in a ...-service.xml file.
Thanks. -
2. Re: Stateful Session bean unable to be exposed as a WS
thomas.diesler Dec 21, 2004 5:06 AM (in response to starksm64)SOAP does not support the notion of a session identifier at the message level and not every transport has session connections.
The way you implement stateful web service access is to introduce an application specific header element that can be read/write by JAXRPC handlers -
3. Re: Stateful Session bean unable to be exposed as a WS
thomas.diesler Jan 3, 2005 1:26 PM (in response to starksm64)Adrian Wilford wrote:
I assume that you mean here that my app must create a session identifier, and then put that into a special header element?
I suspect that I would probably also have to do the mapping from the session identifier to the corresponding handle to the stateful session bean?
Could you possibly point me to where I could find out some more info on how to do this?
Thanks for your time & kind regards,
Adrian -
4. Re: Stateful Session bean unable to be exposed as a WS
will.tatam Sep 27, 2011 8:28 AM (in response to thomas.diesler)Did you ever find out how to get back the handle for a given stateful bean ?