DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7856>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7856 using call.setTargetEndpointAddress in a header processor on the client side does not affect the target url ------- Additional Comments From [EMAIL PROTECTED] 2002-04-16 22:35 ------- There may be valid reasons for modifying the call object (at least the target address) in a handler. Consider the implementation of WS-Routing. Here, on the client side, a WS-Routing request handler will typically add the WS-Routing <path> header to the outgoing mesage. Depending on whether the message is supposed to travel through an intermediary, the target address will need to change. Note that the client application (the stub that generated the call object) does not (may not) know if the message is supposed to travel via an intermediary. Actually this is the exact specific scenario that required me to change the target address in the handler.
