Chris,
Even then, don't you think that the private method
createMessageContext specified in AxisServlet should
be protected? This may save a lot of code duplication
for applications requiring some control on the
properties of MessageContext.
Currently, the call in buried deep inside both doGet
Shantanu -
Anne pointed out that service names MUST conform to the rules for the xsd:NCName type
(according to the WSDL schema definition) and therefore spaces are invalid.
I was erroneously just focused on the service endpoint URL used by Axis and had
overlooked this fact.
/Chris
--- shanta
Shantanu -
if you post a patch to bugzilla for the encoding issue with a test case, i'll check it
in and apply it. after all, the customer is always right ;) and your use case is a
valid URN.
Have you tried to place the encoded servicename in the WSDD and checking if that
works? for examp
I will post it in bugzilla shortly.
Yes, I have tries the encoded service name and that
works. It is more of a tomcat issue, which is external
to axis, and being able to easily override the
MessageContext param settings should do the trick.
Thanks,
Shantanu
--- chaddad <[EMAIL PROTECTED]> wrote
