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
- RE: client-config.wsdd Glen Daniels
- RE: client-config.wsdd Rajal Shah
- client-config.wsdd Sunil Iyengar
- RE: client-config.wsdd Jorge Lorenzo
- RE: client-config.wsdd Yakulis, Ross (Ross)
- client-config.wsdd Richard Martin
- RE: client-config.wsdd Christophe Roudet
- Re: client-config.wsdd Glen Daniels
- Re: client-config.wsdd Glen Daniels
- RE: client-config.wsdd Senthil_KM
- Re: client-config.wsdd Richard Martin
- Re: client-config.wsdd Davanum Srinivas
- Re: client-config.wsdd Richard Martin
- client-config.wsdd Michael Thompson