[jira] [Assigned] (CXF-4299) wsdl2java cannot create code
[ https://issues.apache.org/jira/browse/CXF-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-4299: - Assignee: Freeman Fang > wsdl2java cannot create code > > > Key: CXF-4299 > URL: https://issues.apache.org/jira/browse/CXF-4299 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 2.5.3 > Environment: jdk1.5.0_22 + j2ee 5 + WINDOWS XP(SP3) >Reporter: bglmmz >Assignee: Freeman Fang > > run the following command: > wsdl2java -p example.adc -d src -all adc.wsdl > and get the following error message: > Exception in thread "main" java.lang.AbstractMethodError: > org.apache.crimson.tree.XmlDocument.setDocumentURI(Ljava/lang/ > String;)V > at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:916) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:231) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:191) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.parseWSDL(WSDLDefinitionBuilder.java:78) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.build(WSDLDefinitionBuilder.java:69) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:84 > ) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:61 > ) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:171) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:138) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:286) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184) > > here is my adc.wsdl > > > http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://adc.siinterface.com/"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; > targetNamespace="http://adc.siinterface.com/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> > > targetNamespace="http://adc.siinterface.com/";> > > > > > > > type="s:string" /> > > > > > > > type="tns:AdcSiRequest" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> > > > > > > name="ADCSIInterfaceResult" type="tns:AdcSiResponse" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:string" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > > > > > http://adc.siinterface.com/ADCSIInterface"; > style="document" /> > > > > > > > > >type="tns:SIInterfaceForADCSoap"> > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > > > > >soapAction="http://adc.siinterface.com/ADCSIInterface"; style="document" /> > > > > > > > > > > binding="tns:SIInterfaceForADCSoap"> >location="http://cmcc.esms.com.cn:8086/SIInterfaceForADC.asmx"; /> > > binding="tns:SIInterfaceForADCSoap12"> >location="http://cmcc.esms.com.cn:8086/SIInterfaceForADC.asmx"; /> > > > -- This message is automatically generated by JIRA. If
[jira] [Commented] (CXF-4299) wsdl2java cannot create code
[ https://issues.apache.org/jira/browse/CXF-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271176#comment-13271176 ] Freeman Fang commented on CXF-4299: --- Hi, The exception Exception in thread "main" java.lang.AbstractMethodError: org.apache.crimson.tree.XmlDocument.setDocumentURI(Ljava/lang/ String;)V is interesting, the crimson here indicate somehow you messed up your environment with old xmlParser API, you should use xerces but not crimson. A quick question, did you endorse crimson jar to your JDK? Btw, I've test your WSDL with CXF 2.5.3, on my machine, it works both with JDK 1.5 and 1.6. Freeman > wsdl2java cannot create code > > > Key: CXF-4299 > URL: https://issues.apache.org/jira/browse/CXF-4299 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 2.5.3 > Environment: jdk1.5.0_22 + j2ee 5 + WINDOWS XP(SP3) >Reporter: bglmmz >Assignee: Freeman Fang > > run the following command: > wsdl2java -p example.adc -d src -all adc.wsdl > and get the following error message: > Exception in thread "main" java.lang.AbstractMethodError: > org.apache.crimson.tree.XmlDocument.setDocumentURI(Ljava/lang/ > String;)V > at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:916) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:231) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:191) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.parseWSDL(WSDLDefinitionBuilder.java:78) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.build(WSDLDefinitionBuilder.java:69) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:84 > ) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:61 > ) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:171) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:138) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:286) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184) > > here is my adc.wsdl > > > http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://adc.siinterface.com/"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; > targetNamespace="http://adc.siinterface.com/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> > > targetNamespace="http://adc.siinterface.com/";> > > > > > > > type="s:string" /> > > > > > > > type="tns:AdcSiRequest" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> > > > > > > name="ADCSIInterfaceResult" type="tns:AdcSiResponse" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:string" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > > > > > http://adc.siinterface.com/ADCSIInterface"; > style="document" /> > > > > > > > > >type="tns:SIInterfaceForADCSoap"> > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > >
[jira] [Created] (CXF-4300) cxf-core does not install on karaf 3 snapshot
Christian Schneider created CXF-4300: Summary: cxf-core does not install on karaf 3 snapshot Key: CXF-4300 URL: https://issues.apache.org/jira/browse/CXF-4300 Project: CXF Issue Type: Bug Components: OSGi Reporter: Christian Schneider Assignee: Christian Schneider Fix For: 2.6.1, 2.5.4 The reason is that the cxf karaf commands require the karaf version to be below 3.0.0. I will increase the import range to [2.2,4). For this to work the linked karaf issue also will have to be solved. -- 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
[jira] [Closed] (CXF-4299) wsdl2java cannot create code
[ https://issues.apache.org/jira/browse/CXF-4299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bglmmz closed CXF-4299. --- Resolution: Not A Problem Fix Version/s: 2.5.4 Sorry, it's my env problem... > wsdl2java cannot create code > > > Key: CXF-4299 > URL: https://issues.apache.org/jira/browse/CXF-4299 > Project: CXF > Issue Type: Bug > Components: Core >Affects Versions: 2.5.3 > Environment: jdk1.5.0_22 + j2ee 5 + WINDOWS XP(SP3) >Reporter: bglmmz >Assignee: Freeman Fang > Fix For: 2.5.4 > > > run the following command: > wsdl2java -p example.adc -d src -all adc.wsdl > and get the following error message: > Exception in thread "main" java.lang.AbstractMethodError: > org.apache.crimson.tree.XmlDocument.setDocumentURI(Ljava/lang/ > String;)V > at org.apache.cxf.staxutils.StaxUtils.read(StaxUtils.java:916) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:231) > at > org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:191) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.parseWSDL(WSDLDefinitionBuilder.java:78) > at > org.apache.cxf.wsdl11.WSDLDefinitionBuilder.build(WSDLDefinitionBuilder.java:69) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:84 > ) > at > org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.build(JAXWSDefinitionBuilder.java:61 > ) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:171) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:138) > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:286) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at org.apache.cxf.tools.wsdlto.WSDLToJava.main(WSDLToJava.java:184) > > here is my adc.wsdl > > > http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:tns="http://adc.siinterface.com/"; > xmlns:s="http://www.w3.org/2001/XMLSchema"; > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; > targetNamespace="http://adc.siinterface.com/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> > > targetNamespace="http://adc.siinterface.com/";> > > > > > > > type="s:string" /> > > > > > > > type="tns:AdcSiRequest" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> > > > > > > name="ADCSIInterfaceResult" type="tns:AdcSiResponse" /> > > > > > >type="s:string" /> >type="s:string" /> >type="s:int" /> >type="s:string" /> >type="s:string" /> >/> >/> >/> >type="s:string" /> >type="s:string" /> >type="s:string" /> >type="s:string" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > > > > > http://adc.siinterface.com/ADCSIInterface"; > style="document" /> > > > > > > > > >type="tns:SIInterfaceForADCSoap"> > http://schemas.xmlsoap.org/soap/http"; /> > > http://adc.siinterface.com/HelloWorld"; > style="document" /> > > > > > > > > >soapAction="http://adc.siinterface.com/ADCSIInterface"; style="document" /> > > > > > > > > > > binding="tns:SIInterfaceForADCSoap"> >location="http://cmcc.esms.com.cn:8086/SIInterfaceForADC.asmx"; /> > > binding="tns:SIInterfaceForADCSoap12"> >location="http://cmcc.esms.com.cn:8086/SIInterfaceFor
[jira] [Commented] (CXF-4281) uribuilder from null?
[ https://issues.apache.org/jira/browse/CXF-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271281#comment-13271281 ] Sergey Beryozkin commented on CXF-4281: --- Romain, please also watch http://java.net/jira/browse/JAX_RS_SPEC-194 > uribuilder from null? > - > > Key: CXF-4281 > URL: https://issues.apache.org/jira/browse/CXF-4281 > Project: CXF > Issue Type: Bug >Reporter: Romain Manni-Bucau > > in tomee/openejb we need to patch the uri builder to be able to satisfied > some cases (UriBuilder.fromPath(null) for instance) > here is the patched builder working for us: > http://svn.apache.org/repos/asf/openejb/trunk/openejb/server/openejb-cxf-rs/src/main/java/org/apache/openejb/server/cxf/rs/OpenEJBRuntimeDelegateImpl.java > any way to get it merged with cxf? -- 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
[jira] [Commented] (CXF-4295) Update Jetty to latest 7.x.
[ https://issues.apache.org/jira/browse/CXF-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271361#comment-13271361 ] Gary D. Gregory commented on CXF-4295: -- OK, thank you for the update Dan. > Update Jetty to latest 7.x. > --- > > Key: CXF-4295 > URL: https://issues.apache.org/jira/browse/CXF-4295 > Project: CXF > Issue Type: Improvement >Affects Versions: 2.6 > Environment: java version "1.7.0_03" > Java(TM) SE Runtime Environment (build 1.7.0_03-b05) > Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode) > Windows 7 64-bit. >Reporter: Gary D. Gregory >Assignee: Daniel Kulp > Fix For: 2.6 > > > Hi All, > We embed both CXF and Jetty in our app server and would like to use the > latest and greatest CXF and Jetty. Is the latest Jetty 7.x appropriate for > CXF 2.6? Is Jetty 8.x still planned for a Java 6 only future CXF? > Thank you, > Gary -- 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
[jira] [Commented] (CXF-4290) Allow user-specified classloader for JAXRSClientFactory
[
https://issues.apache.org/jira/browse/CXF-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271423#comment-13271423
]
Sergey Beryozkin commented on CXF-4290:
---
I agree that providing an option to specify a custom loader in cases where the
loader of the service class does not see the runtime classes is useful. I'm
also adding a basic utility loader - this can be optimized over time as needed.
> Allow user-specified classloader for JAXRSClientFactory
> ---
>
> Key: CXF-4290
> URL: https://issues.apache.org/jira/browse/CXF-4290
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 2.5
> Environment: Apache Karaf 2.2.4, CXF 2.5.0
>Reporter: Chris Dolan
>
> I wrote a helper class that isolates CXF's JAXRSClientFactory from users. My
> helper exposes this interface as a OSGi service:
> {code}
> public interface JaxRsClientBuilder {
> T createClient(@Nonnull String baseUrl, @Nonnull Class
> resourceApiClass);
> }
> {code}
> However, I discovered a blocking problem. If the user of my helper doesn't
> import org.apache.cxf.jaxrs.client in its OSGi classloader, then I get
> exceptions from java.lang.reflect.Proxy because there's no classloader
> anywhere that can see both resourceApiClass and
> org.apache.cxf.jaxrs.client.Client. I tried a solution (based on
> http://blog.osgi.org/2008/08/classy-solutions-to-tricky-proxies.html) where I
> dynamically make an aggregate classloader that can see both resourceApiClass
> and Client. I think I can trick JAXRSClientFactory into using this new
> classloader for the main resource (by passing in a new Proxy instance as the
> resource class), but I can't wedge my custom classloader in for subresources
> because of the way ClientProxyImpl.invoke() calls JAXRSClientFactory.
> I request the following as a possible solution. Certainly, I'd accept a
> better solution. For example, it looks like JAX-RS 2.0 should eliminate this
> problem by making Client into a public interface instead of an implementation
> detail.
> 1) add a new method variant to JAXRSClientFactory that takes a classloader
> 2) pass this classloader to JAXRSClientFactoryBean, and use it instead of
> cri.getServiceClass().getClassLoader() or the thread context classloader
> 3) change ClientProxyImpl to save this classloader and use it for
> subresources
> See also the following which describes my failed attempt to work around this
> issue:
> http://stackoverflow.com/questions/10458378/how-can-i-make-a-java-lang-reflect-proxy-from-two-separate-classloaders
--
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
[jira] [Commented] (CXF-4290) Allow user-specified classloader for JAXRSClientFactory
[
https://issues.apache.org/jira/browse/CXF-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271444#comment-13271444
]
Sergey Beryozkin commented on CXF-4290:
---
See r1336221 on 2.5.4-SNAPSHOT; please confirm it works for you.
> Allow user-specified classloader for JAXRSClientFactory
> ---
>
> Key: CXF-4290
> URL: https://issues.apache.org/jira/browse/CXF-4290
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
>Affects Versions: 2.5
> Environment: Apache Karaf 2.2.4, CXF 2.5.0
>Reporter: Chris Dolan
>
> I wrote a helper class that isolates CXF's JAXRSClientFactory from users. My
> helper exposes this interface as a OSGi service:
> {code}
> public interface JaxRsClientBuilder {
> T createClient(@Nonnull String baseUrl, @Nonnull Class
> resourceApiClass);
> }
> {code}
> However, I discovered a blocking problem. If the user of my helper doesn't
> import org.apache.cxf.jaxrs.client in its OSGi classloader, then I get
> exceptions from java.lang.reflect.Proxy because there's no classloader
> anywhere that can see both resourceApiClass and
> org.apache.cxf.jaxrs.client.Client. I tried a solution (based on
> http://blog.osgi.org/2008/08/classy-solutions-to-tricky-proxies.html) where I
> dynamically make an aggregate classloader that can see both resourceApiClass
> and Client. I think I can trick JAXRSClientFactory into using this new
> classloader for the main resource (by passing in a new Proxy instance as the
> resource class), but I can't wedge my custom classloader in for subresources
> because of the way ClientProxyImpl.invoke() calls JAXRSClientFactory.
> I request the following as a possible solution. Certainly, I'd accept a
> better solution. For example, it looks like JAX-RS 2.0 should eliminate this
> problem by making Client into a public interface instead of an implementation
> detail.
> 1) add a new method variant to JAXRSClientFactory that takes a classloader
> 2) pass this classloader to JAXRSClientFactoryBean, and use it instead of
> cri.getServiceClass().getClassLoader() or the thread context classloader
> 3) change ClientProxyImpl to save this classloader and use it for
> subresources
> See also the following which describes my failed attempt to work around this
> issue:
> http://stackoverflow.com/questions/10458378/how-can-i-make-a-java-lang-reflect-proxy-from-two-separate-classloaders
--
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
[jira] [Created] (CXF-4301) Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marsh
Andreas Gudian created CXF-4301:
---
Summary: 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
Reporter: Andreas Gudian
(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
[jira] [Issue Comment Edited] (CXF-4301) Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or R
[
https://issues.apache.org/jira/browse/CXF-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271467#comment-13271467
]
Andreas Gudian edited comment on CXF-4301 at 5/9/12 2:54 PM:
-
Attached an example of the error.
The two WSDL files are 100% equal. Creating a copy was just my workaround to
perform the source generation twice within one pom: once with ext. soap headers
= true, once with false.
call {{mvn clean test}} to execute all four test cases. Three of them will fail
due to the problem described here.
was (Author: agudian):
Example of the error.
The two WSDL files are 100% equal. Creating a copy was just my workaround to
perform the source generation twice within one pom: once with ext. soap headers
= true, once with false.
call {{mvn clean test}} to execute all four test cases. Three of them will fail
due to the problem described here.
> 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
>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
[jira] [Updated] (CXF-4301) Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marsh
[
https://issues.apache.org/jira/browse/CXF-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated CXF-4301:
Attachment: implicit-header-showcase.zip
Example of the error.
The two WSDL files are 100% equal. Creating a copy was just my workaround to
perform the source generation twice within one pom: once with ext. soap headers
= true, once with false.
call {{mvn clean test}} to execute all four test cases. Three of them will fail
due to the problem described here.
> 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
>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
[jira] [Created] (CXF-4302) apache-cxf-2.6.0.zip distribution doesn't contain org.springframework.web-3.0.7.RELEASE.jar
Serhiy Yakovyn created CXF-4302: --- Summary: apache-cxf-2.6.0.zip distribution doesn't contain org.springframework.web-3.0.7.RELEASE.jar Key: CXF-4302 URL: https://issues.apache.org/jira/browse/CXF-4302 Project: CXF Issue Type: Bug Components: Configuration Affects Versions: 2.6 Reporter: Serhiy Yakovyn apache-cxf-2.6.0.zip (downloaded from http://apache-mirror.telesys.org.ua/cxf/2.6.0/apache-cxf-2.6.0.zip) package doesn't contain org.springframework.web-3.0.7.RELEASE.jar This causes an issue when running CXF based Web Services within Eclipse: "SEVERE: Servlet /WorkdayNotification threw load() exception java.lang.ClassNotFoundException: org.springframework.web.context.WebApplicationContext" -- 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
[jira] [Resolved] (CXF-4279) WS-Security ehcache things never shutdown
[ https://issues.apache.org/jira/browse/CXF-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4279. -- Resolution: Fixed Fix Version/s: 2.4.8 > WS-Security ehcache things never shutdown > - > > Key: CXF-4279 > URL: https://issues.apache.org/jira/browse/CXF-4279 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.5.3, 2.6 >Reporter: Daniel Kulp >Assignee: Daniel Kulp > Fix For: 2.6.1, 2.5.4, 2.4.8 > > > The two ehcache implementations (TokenStore and ReplayCache) create > CacheManager instances. However, nothing currently calls shutdown on the > instances. Since the cachemanager has a non-daemon thread pool, this blocks > things like tomcat from shutting down cleanly. -- 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
[jira] [Resolved] (CXF-4302) apache-cxf-2.6.0.zip distribution doesn't contain org.springframework.web-3.0.7.RELEASE.jar
[ https://issues.apache.org/jira/browse/CXF-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4302. -- Resolution: Fixed Fix Version/s: 2.6.1 Assignee: Daniel Kulp Already fixed (in svn revision 1331587) on trunk for the 2.6.1-SNAPSHOTs > apache-cxf-2.6.0.zip distribution doesn't contain > org.springframework.web-3.0.7.RELEASE.jar > --- > > Key: CXF-4302 > URL: https://issues.apache.org/jira/browse/CXF-4302 > Project: CXF > Issue Type: Bug > Components: Configuration >Affects Versions: 2.6 >Reporter: Serhiy Yakovyn >Assignee: Daniel Kulp > Fix For: 2.6.1 > > > apache-cxf-2.6.0.zip (downloaded from > http://apache-mirror.telesys.org.ua/cxf/2.6.0/apache-cxf-2.6.0.zip) package > doesn't contain org.springframework.web-3.0.7.RELEASE.jar > This causes an issue when running CXF based Web Services within Eclipse: > "SEVERE: Servlet /WorkdayNotification threw load() exception > java.lang.ClassNotFoundException: > org.springframework.web.context.WebApplicationContext" -- 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
[jira] [Updated] (FEDIZ-10) improved federation configuration
[ https://issues.apache.org/jira/browse/FEDIZ-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Wulff updated FEDIZ-10: -- Component/s: Plugin > improved federation configuration > - > > Key: FEDIZ-10 > URL: https://issues.apache.org/jira/browse/FEDIZ-10 > Project: CXF-Fediz > Issue Type: Improvement > Components: Plugin >Reporter: Juerg Portmann >Assignee: Oliver Wulff > Attachments: file.patch > > > improved federation configuration, > changed implementation to use declarative xml based configuration instead of > hardcoded approach -- 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
[jira] [Updated] (CXF-4301) Problem with Implicit Soap Headers and @ResponseWrapper in methods with multiple response attributes: NullPointerException in ReflectionServiceFactoryBean or Response-Marsh
[
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
