We use Apache SOAP with Weblogic 5.1 and are migrating it to 6.1.
The problem with the Weblogic implementation of SOAP is that it has no way
to support session state - so all of your services must be stateless. This
is as per the SOAP spec, but is useless for us. With Apache SOAP you can
choose
This looks like a null object to me, with xsi:null='1':
Wouldn't an empty Person object look like
"John Mani"
Our clients are using MS XML but not SOAP, and can't use cookies.
We set cookies on the server (set them in the header) but get our MS
clients to rewrite those cookies into the URL for their next request, as
they can read the headers and write to URLs but not set cookies.
Is MS SOAP the same?
Why don't you set up the servlet to be container protected and allow the
container to do the basic authentication? We do this with weblogic and
apache SOAP and it works well. An unauthenticated user gets a 401
unauthorized and can reply with the basic authentication header. An
unauthenticated use
Sounds obvious, but are you sure that you are deploying your EJB? I would
write a test harness in Java that runs on your application server to check
that. It looks to me like you can't call the EJB at all, either through EJB
deployment, or maybe you've got your JNDI properties set up incorrectly.
