Follow-up: I have the same behaviour when I set the handlers on the call (setClientHandlers). It's already enough to invoke the method with an empty chain to get the described behaviour.
Tested with 1.2beta1 and 1.2beta2. What's wrong here? Yves On Mon, 2004-07-19 at 11:31, Yves Langisch wrote: > All, > > I have a document/literal web service which I invoke through the > wsdl2java generated stub. So far everything is okay. Now, if I create a > client-config.wsdd to define some handlers, it seems that the > client-config.wsdd overrides the encoding settings made by the stub > although there is no encodingStyle -> call seems to be soap-encoded > instead of literal afterwards. Following the client-config.wsdd: > > <?xml version="1.0" encoding="UTF-8"?> > <deployment name="defaultClientConfig" > xmlns="http://xml.apache.org/axis/wsdd/"; > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> > <transport name="http" > pivot="java:org.apache.axis.transport.http.HTTPSender"/> > <transport name="local" > pivot="java:org.apache.axis.transport.local.LocalSender"/> > <transport name="java" > pivot="java:org.apache.axis.transport.java.JavaSender"/> > <service name="SalaryDeclaration"> > <requestFlow> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/> > </requestFlow> > <responseFlow> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/> > </responseFlow> > </service> > </deployment> > > Is this a normal behaviour? > > Yves
