On Thursday, January 19, 2012 3:21:24 PM Marc SCHNEIDER wrote: > Thanks for your answer, > > Ok I'd rather use Aegis because it supports maps and collections out > of the box. So I'll switch to the simple frontend.
The JAXWS frontend should be fine. I don't understand what you mean by "the fieldName parameter is not taken in account." We'd likely need to see the generated WSDL as well as the SOAP message that is being sent to make sure the two of them match. Once common issue between JAX-WS and Aegis is that Aegis generally prefers qualified schemas whereas JAX-WS generally produces unqualified. Thus, making sure the soap message meets the correct requirements can sometimes be challenging. Dan > > Marc. > > On Thu, Jan 19, 2012 at 11:35 AM, Hannes Holtzhausen > > <[email protected]> wrote: > > Try using the JAXB databinding. > > > > CXF prefers: > > > > Simple Frontend -> Aegis databinding > > JaxWs Frontend -> JAXB databinding > > > > > > On Thu, Jan 19, 2012 at 12:20 PM, Marc SCHNEIDER > > > > <[email protected]> wrote: > >> Hello, > >> > >> I'm a newbie to cxf and I try to call a web service method with a > >> parameter but this one is not taken in account (null is received). > >> > >> I'm using : > >> cxf 2.5.1 with jax-ws front end > >> aegis databinding > >> spring 3.0.6 > >> > >> Here is my Spring configuration : > >> http://pastebin.com/zJnAbF4n > >> > >> Java web service classes : > >> http://pastebin.com/jcdqiCUT > >> > >> So when calling the uniqueValues method, the fieldName parameter is > >> not taken in account. > >> > >> Any idea? > >> > >> Thanks in advance, > >> Marc. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
