I haven't tried it with Borland, but I have done it on my own using Pramati Server (which means I had to install Axis myself into the EJB Server) and it works.
Here is what your deployment descriptor should look like: <service name="myEJB" provider="java:EJB"> <parameter name="allowedMethods" value="sayHello"/> <parameter name="beanJndiName" value="Test_TestSP1EJB_TestSP1"/> <parameter name="jndiURL" value="rmi://localhost:9191"/> <parameter name="jndiContextClass" value="com.pramati.naming.client.PramatiClientContextFactory"/> <parameter name="homeInterfaceName" value="com.romulin.TestHome"/> </service> NOTE: You will need to change the jndiContextClass and jndiURL to match Borland's. Also, you can only use Stateless beans. If you want any kind of state, you would do better to put a java class in front of the EJB and create it as a regular web service. ----- Original Message ----- From: "Giordano Vicoli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 10, 2002 4:10 AM Subject: Axis and EJB with Borland Enterprise Server > Hello, > > I am Giordano Vicoli from Italy. > > As you know Borland Enterprise Server (BES) enables the deploy of Axis Web > Services. > I have the BES 5.0.1 that implements Axis Alpha 3 release. In the sample > code there is > an example of an EJB exposed as a Web Service. I tried it but it doesn't > work. > > Has someone tried this example or other similar examples? > > Thanks a lot for the answer. > > Bye, > Giordano >
