Hmm... actually, on a one way request, we probably should completely remove the HttpServletRequest/Response from the message. They are no longer valid at that point.
Basically, once we're done parsing the message, if the operation is a one way, we return and empty 200 response back to the client (per spec) and close them all off which thus would invalidate the request/response objects. That's probably what you are seeing. Dan On Thu April 2 2009 1:37:12 pm rkiesler wrote: > In my interceptor code, I'm trying to obtain the servlet's HTTP port using > the following code: > > > HttpServletRequest request = > (HttpServletRequest)message.get(AbstractHTTPDestination.HTTP_REQUEST); > > int port = request.getLocalPort(); > > If the message is for a request/response operation, this works fine, and > the port is reported correctly as 8080. If the operation is a one-way > operation (e.g., using hello_world_soap12 sample's greetMeOneWay > operation), the port is reported as -1, and additionally, the headers map > is null, as are most of the ServletRequest properties, like contextPath, > requestUrl, etc. > > Any insights would be appreciated. > > -- > > Roy -- Daniel Kulp [email protected] http://www.dankulp.com/blog
