axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Reopened] (AXIS2-5024) Issue in setting transport headers in Axis2 local transport
Date Sat, 14 May 2011 15:38:47 GMT


Andreas Veithen reopened AXIS2-5024:

By definition, transport headers are generated by an outgoing transport and processed by the
incoming transport. However, the local transport doesn't have any concept of transport header.

The only use case for "propagating" transport headers would be a service client that sends
additional information to a service via these transport headers. This however is not a valid
use case because a service is not supposed to mess with transport headers. Indeed, this would
be in contradiction with the concept of transport independence which is fundamental to SOAP.

Therefore I think that this issue (with its current description) is invalid. I don't know
what you are trying to achieve here, but my feeling is that you are using the concept of "transport"
for something that it was not designed for.

> Issue in setting transport headers in Axis2 local transport
> -----------------------------------------------------------
>                 Key: AXIS2-5024
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.5.4
>            Reporter: Heshan Suriyaarachchi
>             Fix For: 1.6.0, nightly
>         Attachments: AXIS2-5024-patch.diff
> Transport headers are not properly set in the Axis2 local transport. Therefore, already
set transport headers are not propagated correctly.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message