cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Gudian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-4301) Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marshalling Error
Date Thu, 10 May 2012 06:08:11 GMT

     [ https://issues.apache.org/jira/browse/CXF-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andreas Gudian updated CXF-4301:
--------------------------------

    Affects Version/s: 2.5.3
                       2.6
    
> Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response
attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marshalling Error
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4301
>                 URL: https://issues.apache.org/jira/browse/CXF-4301
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.5.3, 2.6
>            Reporter: Andreas Gudian
>         Attachments: implicit-header-showcase.zip
>
>
> (Extended version of the problem described and fixed in CXF-4117)
> I have a WSDL that defines an implicit Soap Header for requests and responses. One of
the response messages consists of multiple elements with types that map to the same type in
Java (String, in that case).
> Problem #1: When I generate my Code using the flag {{ExtendedSoapHeaders=true}}, the
service can not be published due to the following exception:
> {code}
> java.lang.NullPointerException
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeParameter(ReflectionServiceFactoryBean.java:827)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeClassInfo(ReflectionServiceFactoryBean.java:748)
> 	at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.initializeWSDLOperation(JaxWsServiceFactoryBean.java:254)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeWSDLOperations(ReflectionServiceFactoryBean.java:652)
> 	at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.initializeWSDLOperations(JaxWsServiceFactoryBean.java:292)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromWSDL(ReflectionServiceFactoryBean.java:393)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:506)
> 	at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:242)
> 	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.ServerFactoryBean.create(ServerFactoryBean.java:159)
> 	at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:207)
> {code}
> Problem #2: When I generate my Code using the flag {{ExtendedSoapHeaders=false}}, the
response message is not marshaled correctly and the schema validation fails (the element from
the Soap header is placed in the response body, filled with the value of one of the regular
response elements, which then was missing the response).
> I will attach an example for both cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message