I have the same problem here. I think that the culprit is the
element in the WSDL. This binding forces the WSDL2Java to generate code that
sends the application/x-www-form-urlencoded header. This corresponds to the
REST style of web service invocation. However, I think that this REST
approach d
On Sat, May 31, 2008 at 7:57 AM, Eran Chinthaka <[EMAIL PROTECTED]>
wrote:
> Keith,
>
> I think enabling https, will allow the "client" to access the service over
> https. But the question seems to be how to tell axis2 about the new https
> transport receiver. I also like to know the answer to thi
One more question. Why are you interested only on SOAPAction to determine
the operation? (FYI : Operation name can be in Contenttype (SOAP 1.2) or in
the URL itself )
Anyway, the code I pasted earlier will work. But the operation name should
be available within message context. Try messageContext.
