Are you configured from Spring or the API? Either way, you have to use the JaxWs factory or the JAX-WS standard classes, NOT the Simple... classes. Perhaps you could post up some configuration?
On Sat, Nov 1, 2008 at 7:43 PM, JuliusIT <[EMAIL PROTECTED]> wrote: > > Thanks for the reply > > 1) 2.1 > 2) JAXWS, i suppose, as i setted it in the and build for the > org.apache.cxf.tools.wsdlto.WSDLToJava and > org.apache.cxf.tools.java2ws.JavaToWS class. > > I see many question and many response on the forum like > > http://www.nabble.com/Webservice-client-sending-null-parameters-to-host-td15368060.html > > or > > http://www.nabble.com/Strange-unmarshalling-error.-Request-parameter-becomes-null.-td19188748.html#a19188748 > > but i dont'use (maybe I'm wrong) any JaxWsProxyFactoryBean. > > > 1) What version of CXF. > 2) What front end and data binding. > > ? > > > On Sat, Nov 1, 2008 at 10:03 AM, JuliusIT <[EMAIL PROTECTED]> wrote: >> >> Noone has an idea? Please help me... it' s days i'm hitting my head on >> the >> screen... >> I tryed all the solution i find in forum and web. Noone Works. If the >> parameter and the response is a simple type there is no problem. As soon >> as >> the parameter are object they are all set to null when i debug it on the >> server. I red that is a problem of qualified/unqualified simple /jaxws >> frontend. What I don't understand is how if I do: >> >> CXF Server--> WSDL --> CXF client >> >> things don't works. >> > > > -- > View this message in context: > http://www.nabble.com/Null-parameter-in-request-and-response-tp20255751p20285540.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
