>
> How are you generating your client-side message ? Are you not using
> HeaderList.fillRequestAddressingHeaders(...) ?
Right now the mex client request is just a hard coded string -- at tool
time there are no pipes to use so I'm not dealing with Packets. In the
future, it'd be good to integrate the mex code better with the runtime
code. Even then, I had assumed that the mex client would be something
closer to a jax-ws proxy or dispatch object. But there may be a case,
like retrieving a wsdl at runtime, that we'd be in the pipeline already
and need to retrieve this, and so that would be useful for creating the
request (which is just an empty body + the mex action header + the ws-a
headers that would be added by jaxws/wsa).
Thanks.
>
> I don't see a reason where Action will need to be overridden for a given
> WSBinding and WSDLPort. Only protocol messages would like to override
> the Action property and so I'll change the client side method
> accordingly as well.
Yep, that makes sense to me.
Cheers,
Bobby