Commentaires sur : Apache CXF Clients : null result when using bad client factory http://planet.petalslink.com/home/chamerling/2009/04/09/apache-cxf-clients-null-result-when-using-bad-client-factory/ Things around SOA, Web Services, Open Source and more... Tue, 13 Oct 2009 10:09:57 +0000 hourly 1 http://wordpress.org/?v=3.1.2 Par : JMarc Bailly http://planet.petalslink.com/home/chamerling/2009/04/09/apache-cxf-clients-null-result-when-using-bad-client-factory/comment-page-1/#comment-80 JMarc Bailly Thu, 07 May 2009 11:43:19 +0000 http://blog.ebmwebsourcing.com/home/chamerling/?p=91#comment-80 Hi, Greats that you mention it. But using the 'JaxWsProxyFactoryBean' is also helpful for the WebParam definition. If you use the 'bad' ClientWsProxyFactoryBean, your client will not recognize the name of your specified 'WebParam' name, it will use the default convention : arg0 (if there's only one parameter) example. @WebService(name="myClass") public interface myClass { @WebMethod(operationName="myMethod") public String myMethod(@WebParam("myArg") String myArg); } This will result in a triggering a Fault. Hi,

Greats that you mention it.

But using the ‘JaxWsProxyFactoryBean’ is also helpful for the WebParam definition.

If you use the ‘bad’ ClientWsProxyFactoryBean, your client will not recognize the name of your specified ‘WebParam’ name, it will use the default convention : arg0 (if there’s only one parameter)

example.

@WebService(name= »myClass »)
public interface myClass {
@WebMethod(operationName= »myMethod »)
public String myMethod(@WebParam(« myArg ») String myArg);
}

This will result in a triggering a Fault.

]]>