[jira] Commented: (AXIS2-278) Addressing Out handler being engaged twice in the out flow

["Jiří Hanuš (JIRA)" <ji...@apache.org>]

    [ http://issues.apache.org/jira/browse/AXIS2-278?page=comments#action_12332598 ] 

Jiří Hanuš commented on AXIS2-278:
----------------------------------

Doesn't. For each client's request, headers are populated with new set of wsa:.. . So third request has 3x addressing headers, and so on. Each instantiation of client stub adds a new addressing handler into service outflow.

The problem is, that each Stub instantiation fires building Flows for all service' operations (PhaseResolver.buildChains()). It seems that this operation populates service's handler chains with module and global ones, but the base Stub class has a __static__ filed which holds this information for particular service. So, when the stub is instantiated second time, handlers are duplicated in the service's chains.

There is a little 'clash' between the static field for service description and running config builder in constructor.

I've fixed it locally as follows, but its a bit dirty:
 1) make field "_service" non-static in class Stub
 2) move entire "static {}" block of generated stub into init() method and call it in the constructor as the first thing

Regards,
 Jiri

> Addressing Out handler being engaged twice in the out flow
> ----------------------------------------------------------
>
>          Key: AXIS2-278
>          URL: http://issues.apache.org/jira/browse/AXIS2-278
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: deployment
>     Reporter: Eran Chinthaka
>     Assignee: Deepal Jayasinghe
>      Fix For: 0.93

>
> One can see two copies of addressing headers in the OUT message. The reason for this seems to be that the addressing out handler is being engaged twice in the out flow. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira