Thanks for all your replies.
As I originally suspected, the problem was a JNDI naming problem.
As I know how frustating it can be for someone starting to get all this going, I'll
give a short explanation what I did to get it working.
Here is the deployment descriptor:
?xml version=1.0?
Fergus,
Thanks for letting us know what worked for you. I have added a section
to the iPlanet installation instructions showing your deployment
descriptor.
Scott Nichol
- Original Message -
From: Fergus O'Dalaigh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 19, 2002
Hi, I've deployed normal Java classes as services on the SOAP web app, but I really
need to use EJB's as services.
I'm using iAS 6.0 (iPlanet Application Server) and SOAP 2.3.1.
I get a Unable to initialize context error when I run my SOAP client.
Here is my SOAP deployment descriptor:
?xml
Here's a Sun iPlanet sample description. At the bottom, I notice that
ContextProviderURL is left blank.
Scott Nichol
- Original Message -
From: Fergus O'Dalaigh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 14, 2002 3:40 AM
Subject: Unable to initialize context error
Actually, here it is:
http://developer.iplanet.com/appserver/samples/helloworld_soap/docs/inde
x.html.
Scott Nichol
- Original Message -
From: Scott Nichol [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 14, 2002 6:05 PM
Subject: Re: Unable to initialize context error
one way would be to tweak
org/apache/soap/providers/StatelessEJBProvider.java to use the
following mechanism to create the InitialContext . iAS 6.0 supports the
no args mechanism of creating the IntitialContext inside the container .
try
{
/// current mechanism
javax.naming.InitialContext
