-
1. Re: first experiences with JBossWS: no serializer found
starksm64 Oct 5, 2004 10:11 PM (in response to rickkw)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