-
1. Re: first experiences with JBossWS: no serializer found
thomas.diesler Aug 10, 2004 7:09 AM (in response to lafr)When generating the wsdd, JBossWS looks for additional META-INF/ws4ee-deployment.xml descriptor and when found merges the operations and type mappings with the generated wsdd. For java service endpoints this descriptor should be located in WEB-INF/ws4ee-deployment.xml.
In your case the ws4ee-deployment.xml would look simmilar to
<deployment
xmlns='http://xml.apache.org/axis/wsdd/'
xmlns:java='http://xml.apache.org/axis/wsdd/providers/java'
xmlns:soap='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2000/10/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<typeMapping
qname='ns1:CustomerOrder' xmlns:ns1='http://org.jboss.webservice/complexbean'
type='java:org.jboss.webservice.complexbean.CustomerOrder'
serializer='org.apache.axis.encoding.ser.BeanSerializerFactory'
deserializer='org.apache.axis.encoding.ser.BeanDeserializerFactory'
encodingStyle=''
/>
<typeMapping
qname='ns1:CustomerOrderPosition' xmlns:ns1='http://org.jboss.webservice/complexbean'
type='java:org.jboss.webservice.complexbean.CustomerOrderPosition'
serializer='org.apache.axis.encoding.ser.BeanSerializerFactory'
deserializer='org.apache.axis.encoding.ser.BeanDeserializerFactory'
encodingStyle=''
/>
For details see: http://www.jboss.org/wiki/Wiki.jsp?page=WSTypeMapping -
2. Re: first experiences with JBossWS: no serializer found
lafr Aug 11, 2004 1:07 PM (in response to lafr)Thanks for your help.
Two small remarks:
1. a typeMapping for CustomerOrder is already in the generated wsdd file in the work dir.
So there is no need to specify it again.
2. I had to fill the encoding style like this:
<typeMapping
qname='ns1:CustomerOrderPosition' xmlns:ns1='http://org.jboss.webservice/complexbean'
type='java:org.jboss.webservice.complexbean.CustomerOrderPosition'
serializer='org.apache.axis.encoding.ser.BeanSerializerFactory'
deserializer='org.apache.axis.encoding.ser.BeanDeserializerFactory'
encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'
/> -
3. Re: first experiences with JBossWS: no serializer found
thomas.diesler Aug 12, 2004 3:55 AM (in response to lafr)Please beware, that SOAP encoding is essentially deprecated and should not be used ws4ee. That leaves you with the choice of document/literal and rpc/literal. There are some useful links on the WIKI if you want to know more about the encoding styles.
SOAP encoding is explicitly forbidden in the WSI-BasicProfile-1.0 for interoperability reasons. See BP-1.0 (R2706)
If your remote party uses SOAP encoding, you have of course no choice. But if you are in control of both sides, you should stick to literal encoding.
cheers -
4. Re: first experiences with JBossWS: no serializer found
kspsoftgroup Mar 30, 2006 11:31 AM (in response to lafr)thomas.diesler@jboss.com
I found that example complexbean doesn't work if types Customer, CustomerArray, CustomerOrder and CustomerOrderPosition moved from package org.jboss.webservice.complexbean to package(for example):
package org.jboss.webservice.model. After that attribute was changed in file ws4ee-deployment.xml, project was recompiled, mappings and wsdl were regenerated. And on invocation of endpoint I had exception: "No serializer found for class....". Tell me please, what i did wrong.