Thanks Samuel Am worried not about how to expose a EJB as web service. I want to know how the server do the lookup and how it works.
JSR109 is "webservices for J2EE" and talk about how to expose J2EE componets as webservices. I want to know how much axis support it. What left to be done :) Thanks for answer.. Srinath On Tue, 2003-09-23 at 20:01, Koller, Shmuel wrote: > Axis exposes a EJB (which can be in remote EJB container - relative to Axis > web container). > You have to deploy in Axis - meaning just define the web-service (java:EBJ, > port of EJB containener, etc). > No piece of code needed on SOAP server side. > > Axis will do the lookup and Expose the EJB - only as SOAP-RPC, you need a > corresponding SOAP-RPC client to drive > the webservice Url (in Axis, in web contained like Tomcat). > > There may still be bug (open until recently) if you want to generate wsdl? > for the web-service thus deployed. > > Do not know JSR 109, Shmuel Koller > > -----Original Message----- > From: Srinath Perera [mailto:[EMAIL PROTECTED] > Sent: Friday, September 19, 2003 5:43 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: EJB provider and JSR109 > > > Hi All > > Am looking at the JSR109 spec. > > I see that the axis has EJB provider with it. I want to know does EJB > provider gives the minimal functionalty or is it powerful enough to > supply the EJB functionalities the JSR109 speaks about. > > I am only started with it. But to continue it will be very helpful what > are any Limitations (if there is any) in EJB provider. > > Can Anybody give me any pointers. > > Thanks for your time > > Srinath >
