JAXBException: javax.xml.ws.Holder is not known to this context
Hello, I just generated code from my WSDL using CXF maven2 plugin (2.0.5-incubator) The generated service interface uses a HolderString argument as both Request and Response message use the same argument. When I try to invoke the service using local://service adress, I get a serialization error : javax.xml.bind.JAXBException: javax.xml.ws.Holder is not known to this context at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:538) As Holder is an jax-ws API class, I have no idea what I could have missed ... please help ;-) Nico.
Re: JAXBException: javax.xml.ws.Holder is not known to this context
First, setting the Holder argument to null makes my local://service call pass. I get the message payload : soap:Bodyns1:setPayment ... I then found in list archive a similar issue, with solution to use JaxWsProxyFactoryBean fior client. Using this, my Holder is serialized without issue, but the message is wrong : soap:BodySetPayment ... -- Notice the upperCase S This fails to deserialize : org.apache.cxf.interceptor.Fault: Message part { http://33J/services/ServicesCommande/schema}SetPayment was not recognized. (Does it exist in service WSDL?) Nico. 2008/4/15, nicolas de loof [EMAIL PROTECTED]: Hello, I just generated code from my WSDL using CXF maven2 plugin (2.0.5-incubator) The generated service interface uses a HolderString argument as both Request and Response message use the same argument. When I try to invoke the service using local://service adress, I get a serialization error : javax.xml.bind.JAXBException: javax.xml.ws.Holder is not known to this context at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:538) As Holder is an jax-ws API class, I have no idea what I could have missed ... please help ;-) Nico.
Re: JAXBException: javax.xml.ws.Holder is not known to this context
I've found my mistake : reading ( http://cwiki.apache.org/CXF20DOC/local-transport.html) I understood the distinction between simple and Jax-WS frontends. Replacing ServerFactoryBean with Endpoint.publish( local://service, getServiceBean() ); enables the Jax-WS stack and fix my issue. Nico. 2008/4/15, nicolas de loof [EMAIL PROTECTED]: First, setting the Holder argument to null makes my local://service call pass. I get the message payload : soap:Bodyns1:setPayment ... I then found in list archive a similar issue, with solution to use JaxWsProxyFactoryBean fior client. Using this, my Holder is serialized without issue, but the message is wrong : soap:BodySetPayment ... -- Notice the upperCase S This fails to deserialize : org.apache.cxf.interceptor.Fault: Message part { http://33J/services/ServicesCommande/schema}SetPaymenthttp://33J/services/ServicesCommande/schema%7DSetPaymentwas not recognized. (Does it exist in service WSDL?) Nico. 2008/4/15, nicolas de loof [EMAIL PROTECTED]: Hello, I just generated code from my WSDL using CXF maven2 plugin (2.0.5-incubator) The generated service interface uses a HolderString argument as both Request and Response message use the same argument. When I try to invoke the service using local://service adress, I get a serialization error : javax.xml.bind.JAXBException: javax.xml.ws.Holder is not known to this context at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:538) As Holder is an jax-ws API class, I have no idea what I could have missed ... please help ;-) Nico.
wsdl2java and BARE ParameterType
Hello, using a Wsdl first development, is there a wsdl2java argument to force use of SOAPBinding ParameterStyle.BARE ? My WSDL declares Request / Response wrapper objects, and I'd like to get them as is, and not have generated methods with many simple arguments. Nico.
Re: wsdl2java and BARE ParameterType
Thanks, that's not so silly as many of my service arguments are In/Out, so using Holders makes sence. With BARE I'll have to copy Request to Reponse ... But for other reason this will makes my service look better. cheers, Nico. 2008/4/15, Chris McClelland [EMAIL PROTECTED]: Hi Nico, You have to supply a JAXWS binding file which tells CXF to generate the BARE API. See the entry at the bottom of this page: http://cwiki.apache.org/CXF20DOC/wsdl-to-java.html It's silly to default to WRAPPED, but that's what JAXWS demands, so it's not CXF's fault. - Chris nicolas de loof wrote: Hello, using a Wsdl first development, is there a wsdl2java argument to force use of SOAPBinding ParameterStyle.BARE ? My WSDL declares Request / Response wrapper objects, and I'd like to get them as is, and not have generated methods with many simple arguments. Nico.