I have encountered this problem when making SOAP client calls from within
Weblogic 6.1. Strictly speaking, it is a parser bug, but it is one that
could be easily handled by a small change to the Apache code.
The problem is that the getNamespaceURI method of the class that implements
the
I also posted this question to the SOAPBuilders list today. It is really a
WSDL/WSTK/interop question, but I'm hoping someone who has used or helped
develop the WSTK toolkit might have an answer.
WSDL specifies the value of the SOAPAction header at operation level of the
service bindings. This
It is used to specify the value of the SOAPAction HTTP header.
It allows services to be filtered at the servlet level,
before the SOAP envelope is parsed.
See section 6.1.1 of the SOAP spec for details.
I think the value is currently ignored by the Apache server code (true?).
-Original
