I'm working using the ws-fx implementation of WS-Addressing. In fact I've just emailed the fx-dev list with a problem that I've encountered (although I think its a problem in my code rather than the implemenatation!)
Regards,
Richard
Davanum Srinivas wrote:
Richard,
Yes, Please go ahead and add this information to the Wiki. Also just curious, are u using http://ws.apache.org/ws-fx/addressing/ or your own impl? Patches are welcome against the addressing project as well.
thanks, dims
--- Richard Martin <[EMAIL PROTECTED]> wrote:
Thanks Glen, Senthil and Cristophe!
It now works, although I found some interesting things along the way which I thought I should share:
1) I tried putting the client-config.wsdd in the classpath as per Glen's suggestion. This worked, but it worked too well. This caused the AdminClient to fail to deploy the server wsdd (containing the WS-Addressing Handlers) because the client-side WS-Addressing handlers were appending mustUnderstand SOAPHeader elements which the server didn't understand because the server-side WS-Addressing Handlers hadn't been deployed.
2) I tried placing the client-config.wsdd in the working directory, but in order to avoid the problem in 2) I had to move the client execution directory and rearrange the Ant build script so it invoked from another location.
3) The final solution I've settled on is the -D switch to specify it fully.
Should these solutions go in the Wiki? The only thing that I could find relevant to wsdd on the client side is here: http://nagoya.apache.org/wiki/apachewiki.cgi?AxisProjectPages/AxisClientConfiguration
Thanks!
Richard
===== Davanum Srinivas - http://webservices.apache.org/~dims/
