Is the client generated with wsdl2java? If so, you probably want the JaxWsProxyFactoryBean, not the ClientProxyFactoryBean. There probably is a @SOAPBinding annotation on the interface to set it to bare that the ClientProxyFactoryBean isn't picking up.
Dan On Thursday 09 October 2008 6:31:27 am cmoulliard wrote: > The wsdl operation binding has been defined as document/litteral but the > body of the SOAP message generated by the ClientProxyFactoryBean is wrapped > with the operation name which is not what I would like to have in my soap > message. > > Andrew Clegg wrote: > > 2008/10/9 cmoulliard <[EMAIL PROTECTED]>: > >> Apparently, the client sends a wrapped soap message which should not be > >> the > >> case because the style defined in the wsdl port binding section is > >> document/literal !!! > > > > Not sure what you mean here -- 'wrapped' is a style of > > document/literal, all wrapped messages (as far as I know) use > > document/literal binding. > > > > See e.g. > > http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/#N1021 > >A > > > > Andrew. > > ----- > Enterprise Architect > > Xpectis > 12, route d'Esch > L-1470 Luxembourg > > Phone +352 25 10 70 470 > Mobile +352 621 45 36 22 > > e-mail : [EMAIL PROTECTED] > web site : www.xpectis.com www.xpectis.com > My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
