>> Isn't it so that transport is just another handler?
>Yes, but the transport handler chain specific to HTTP will only be invoked for HTTP
>requests.
Ok, this I understand. So this way I won't be using AxisServlet at
all ? This means that my service is not deployed under a webserver ?
Can I
Title: RE: HTTP servlet response
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 10, 2002 9:29 AM
> To: [EMAIL PROTECTED]
> Subject: RE: HTTP servlet response
>
> >I've never done this, but it seems tha
>I've never done this, but it seems that you should be able to write
>a request handler in the HTTP-specific transport chain that does this.
Isn't it so that transport is just another handler ? It also deals
with messagecontext. But than all goes back to AxisServlet, which
eventually sends back
Title: RE: HTTP servlet response
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 10, 2002 6:49 AM
> To: [EMAIL PROTECTED]
> Subject: HTTP servlet response
>
>
> Hi there,
>
> I have a strange questi
destination. Not suer about accessing the HTTP response. hope
this helps.
brenda
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 7:49 AM
To: [EMAIL PROTECTED]
Subject: HTTP servlet response
Hi there,
I have a strange question, it smells
HTTP servlet response stream. Can I do that ? I know
that the response stream is inside the Message somewhere as
a property, but what happens if I send back an error
on that stream ? I saw in the source that the AxisServlet
tries to write the response stream anyway.
Normally the messagcontext would
