cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2673) JaxWsProxyFactoryBean and JaxWsServerFactoryBean communication broken in some cases after upgrade to 2.2.7
Date Tue, 16 Feb 2010 16:53:28 GMT

    [ https://issues.apache.org/jira/browse/CXF-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834303#action_12834303
] 

Daniel Kulp commented on CXF-2673:
----------------------------------


I'll look into the test a bit more, but FYI:  
With JAX-WS, if you define a targetNamespace on the interface, it is definitely best to define
the same targetNamespace on the impl.    Per spec, the namespace on the impl is used for the
namespace for the binding and service parts of the wsdl and the namespace on the interface
is used for the portType and wrapper messages.    If they are different, then you get the
"split wsdl" things.   That is per spec.

I highly recommend making sure the two use the same namespace.






> JaxWsProxyFactoryBean and JaxWsServerFactoryBean communication broken in some cases after
upgrade to 2.2.7
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2673
>                 URL: https://issues.apache.org/jira/browse/CXF-2673
>             Project: CXF
>          Issue Type: Bug
>          Components: Aegis Databinding, JAX-WS Runtime
>    Affects Versions: 2.2.7
>            Reporter: Jara Cesnek
>            Assignee: Daniel Kulp
>            Priority: Blocker
>             Fix For: 2.2.7
>
>         Attachments: cxf-2673-cxf-jaxws-aegis-testcase.zip
>
>
> When using JaxWsProxyFactoryBean and JaxWsServerFactoryBean with AegisDataBinding some
interfaces is broken and all methods call result in NULL.
> When contract interface contains method with parameters of type List<Integer> *AND
NOT CONTAIN* method with return type "List<Integer>" then all methods call return NULL.
> Server code:
> {code}
>         JaxWsServerFactoryBean serverFactoryBean = new JaxWsServerFactoryBean();
>         serverFactoryBean.setServiceClass(AopUtils.getTargetClass(implementor)); //WSImpl.class
>         serverFactoryBean.setServiceBean(implementor);             //WSImpl.class
>         serverFactoryBean.setDataBinding(new AegisDatabinding());
>         serverFactoryBean.setAddress(url);
>         serverFactoryBean.setBus(cxfServlet.getBus());
>         serverFactoryBean.create();
> {code}
> Client code:
> {code}
>             JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
>             factory.setServiceClass(resultInterfaceClass);                 //WS.class
>             factory.setAddress(asURL);
>             factory.setDataBinding(new AegisDatabinding());
>             Object remoteInterfaceImpl = factory.create();
> {code}
> Interface:
> {code}
> @WebService(name="cesnek", targetNamespace="http://ns1")
> public interface WS {
>    
>     Integer zalozNovyDokument(@WebParam(name = "idTypDokument") Integer idTypDokument);
>     void vratDmsDokumenty(@WebParam(name = "idDmsDokumentList") List<Integer> idDmsDokumentList);
>     //When next line is un-commented - bug disappears and all working fine!
>     //List<Integer> vratDmsDokumenty();
> }
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message