It may be hard to believe, but this is almost certainly a classpath
problem. Your service code is loading the definition of SOAPContext
from a different place than the RPCRouter code, so the .class of the
two are not identical.
If you use Tomcat 4, deploy Apache SOAP as a webapp and install yo
Thanks very much Scott. This worked perfect!
Scott Nichol <[EMAIL PROTECTED]> wrote:
The JSP must create a SOAPHTTPConnection for each session in the JSP, then use that SOAPHTTPConnection for each call. The reason is that the SOAPHTTPConnection receives a Cookie in the response that must be resent
Thanks very much Scott. This worked perfect!
Scott Nichol <[EMAIL PROTECTED]> wrote:
The JSP must create a SOAPHTTPConnection for each session in the JSP, then use that SOAPHTTPConnection for each call. The reason is that the SOAPHTTPConnection receives a Cookie in the response that must be resent
The JSP must create a SOAPHTTPConnection for each session in the JSP,
then use that SOAPHTTPConnection for each call. The reason is that
the SOAPHTTPConnection receives a Cookie in the response that must be
resent with subsequent requests in order to associate it with the
same session.
On 10
> NagarajaRao wrote:
>
> Hi ,
> I want to return an Object as a response to a message. How should i
> do it?
> I tried to use SOAPContext.setProperty() at Server and then tried to
> fetch the same at Client. I am getting null. Please let me know.
> At Server:
> SOAPContext resCtx
> resCtx.
