Howdy all- Apache SOAP supported Stateful EJB providers via namespace re-writing. Recall that the SOAP operation can be namespace prefixed. What Apache SOAP does is it changes the URL associated with the operation so that it is unique for each session. Some say it's sleezy but hey it works....
I asked a year or so ago if Axis supported the Stateful EJB provider (mostly because our application is stateful (trying to change that)), and even considered coding it up when the response was: "no". But then I thought about it and came to the conclusion that maybe there exists a reason why the axis developers didn't code a Stateful EJB provider... :) -c On Thu, Dec 04, 2003 at 05:29:47PM +0100, Rodrigo Ruiz wrote: > Hi Keith, some time ago I did some tests on maintaining more than one > session from the same client, but I was unsuccessful. How do you manage > to maintain two instances of your EJB web service? I only managed to > maintain one instance, as I couldn't get two separate sessions :-( > > BTW, perhaps invalidating the session will make the provider to call the > remove() method for you (I haven't read the EJBProvider code). If it is > so, you could modify your client wrapper to encapsulate the session > invalidation in a remove() method :-) > > Cheers, > Rodrigo Ruiz > > Keith Hatton wrote: > > >Well, I didn't see anything saying that only stateless EJBs were supported > >... and stateful beans do work if the client maintains a session, and the > >server scope is set to session. > > > >Keith > > > >-----Original Message----- > >From: Ekbote, Niranjan [mailto:[EMAIL PROTECTED] > >Sent: 04 December 2003 15:25 > >To: '[EMAIL PROTECTED]' > >Subject: RE: Bug? Stateful Session EJB support > > > > > >Has Axis started supporting "Stateful" session beans? I thought for the EJB > >provider, you can only work with "Stateless" session beans. > > > > > > > > > > -- 11:40:00 up 3 days, 1:24, 8 users, load average: 0.05, 0.12, 0.12
