Yes, this is misunderstanding, I simply used the sample quick start code tree as a template. This is why you see the .adb package, but I assure you it's jibx.
DSosnoski wrote: > > Hi Sagi, > > From your exception stack trace, it appears that you're still using > ADB, rather than JiBX: > Anyway, I took your advice regarding TCPmon and found a difference between what SoapUI generates and what Axis2/JIbx generates: SoapUI sends the following request, which works great: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ws="http://ws/"> <soapenv:Body> <ws:testOneArg> <testOneArg0>sagi</testOneArg0> </ws:testOneArg> </soapenv:Body> </soapenv:Envelope> Axis2/jibx sends: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <testOneArg xmlns="http://ws/"> <testOneArg0>sagi</testOneArg0> </testOneArg> </soapenv:Body> </soapenv:Envelope> I found a solution, but it seems somewhat strange: not on the client side, but on the server side: If I added a targetNamespace to the method params as well, the SAME "bad" request now gets invoked correctly, i.e. when changing the web service like so: @WebMethod @WebResult(targetNamespace="http://ws/") public String testOneArg(@WebParam(name="testOneArg0", targetNamespace="http://ws/") String name) { return "Hello " + name; } The Axis2/jibx client works great, and the same request it sent before now gets a proper "Hello john" response... I'm not sure if this is the "correct" solution, but at least it works. The con of this solution, is, of course, the fact that I need to "enforce" things on the service side, which may be 3rd party and out of my control. Is there any better way to do this? thanks -- View this message in context: http://www.nabble.com/AxisFault-when-using-jibx-tp19738701p19739691.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]