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: > 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 example, > 'My%0A%0DService' > > > > > /Chris > > > ---------- Original Message > ---------------------------------- > From: Shantanu Sen <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Wed, 13 Aug 2003 16:22:48 -0700 (PDT) > > >Chris, > > > >I agree that this will be easier. But customers may > >want spaces in their service names for whatever > >reason. > > > >Also, this brings out a problem with the > >MessageContext properties initialization in > >AxisServlet. It forces me to override the get/post > >methods where I could just override the > >createMessageContext method if it was protected. > > > >Probably I should post this axis-dev. > > > >Shantanu > > > >--- chaddad <[EMAIL PROTECTED]> wrote: > >> Shantanu - > >> > >> If you have control over the service, it would be > >> easier to just remove the space from the service > >> name. > >> > >> > >> /Chris > >> > >> > >> ---------- Original Message > >> ---------------------------------- > >> From: Shantanu Sen <[EMAIL PROTECTED]> > >> Reply-To: [EMAIL PROTECTED] > >> Date: Wed, 13 Aug 2003 14:05:55 -0700 (PDT) > >> > >> >Now if the service name has spaces e.g. "My > >> Service", > >> >I see a problem > > > >
