You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2012/11/15 17:32:12 UTC

[jira] [Commented] (CXF-4636) Code generation and runtime do not support portType and binding in different namespaces

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

Glen Mazza commented on CXF-4636:
---------------------------------

Best to reduce the attachment to the simplest possible WSDL that reproduces the problem.  Also, you're claiming the problem is due to the portType and binding being in different namespaces--I take it you've confirmed everything works fine when you have them in the same namespace?
                
> Code generation and runtime do not support portType and binding in different namespaces
> ---------------------------------------------------------------------------------------
>
>                 Key: CXF-4636
>                 URL: https://issues.apache.org/jira/browse/CXF-4636
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime, Soap Binding
>    Affects Versions: 2.6.1, 2.5.6, 2.7.0
>            Reporter: Johannes Rost
>         Attachments: CXF-4636.zip
>
>
> When trying to import a webservice definition with wsdl2java the process fails with a WSDLToJava Error: org.apache.cxf.wsdl11.WSDLRuntimeException: Could not find portType for binding [...]
> This is the case for all three CXF-Version mentioned above as affected.
> When generating Jax-WS classes with wsimport the same exception is thrown when trying to create a Client via CXF/Spring.
> I will add a ZIP-file containing the WSDL- and XSD-files, a sample Spring context XML and the Java-files generated by wsimport shortly.
> The exception is the following:
> org.apache.cxf.wsdl11.WSDLRuntimeException: Could not find portType for binding {http://schemas.microsoft.com/ws/2005/02/mex/bindings}MetadataExchangeHttpBinding_IVsiService. Check wsdl for errors.
> 	at org.apache.cxf.wsdl11.WSDLServiceBuilder.buildServices(WSDLServiceBuilder.java:321)
> 	at org.apache.cxf.wsdl11.WSDLServiceBuilder.buildServices(WSDLServiceBuilder.java:203)
> 	at org.apache.cxf.wsdl11.WSDLServiceFactory.create(WSDLServiceFactory.java:142)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromWSDL(ReflectionServiceFactoryBean.java:412)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:534)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:248)
> 	at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
> 	at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
> 	at org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:90)
> 	at org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactoryBean.java:155)
> 	at org.apache.cxf.jaxws.JaxWsProxyFactoryBean.create(JaxWsProxyFactoryBean.java:156)
> 	at org.apache.cxf.jaxws.spring.JaxWsProxyFactoryBeanDefinitionParser$JAXWSSpringClientProxyFactoryBean.create(JaxWsProxyFactoryBeanDefinitionParser.java:79)
> 	at org.apache.cxf.jaxws.spring.JaxWsProxyFactoryBeanDefinitionParser$JAXWSSpringClientProxyFactoryBean.getObject(JaxWsProxyFactoryBeanDefinitionParser.java:83)
> 	at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142)
> 	... 32 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira