Hi Rodrigo, I have to admit, I haven't tried two clients, but can't see any reason why that shouldn't work.
The EJB in question does a search on a database and pages the result set to the client, that is how I know that the statefulness of the EJB is exposed successfully through Axis. >> perhaps invalidating the session will make the provider to call the remove() method >> for you A nice idea, but "remove" doesn't appear anywhere in the EJB provider. Obviously it was written first and foremost for stateless session EJBs. Although JSR109 only deals with stateless EJBs, there seems no fundamental reason not to expose stateful EJBs if you want to (so long as it doesn't interfere with anything in that spec). All it requires is a client that can handle state too. We are using Axis because it seems to support stateful EJBs better than other providers (GLUE, WASP) and because we want to offer our EJB functionality to .NET and other clients. Keith -----Original Message----- From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] Sent: 04 December 2003 16:30 To: [EMAIL PROTECTED] Subject: Re: Bug? Stateful Session EJB support 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. > > > > >
