As part of the promotion of the Axis project to a top level project, we have decided to create separate mailing lists for Axis 1 and Axis2. For all Axis 1 related questions please subscribe and post to [email protected]. Thanks!
Andreas On Tue, Feb 1, 2011 at 15:36, Marc Carrion <[email protected]> wrote: > Hi, > > I have a .wsdd that I deploy in a axis1.4 server > > <service name="MYService" provider="java:RPC" style="wrapped" use="literal" > xmlns:ns="http://client.my_company.com/MYService/";> > <!-- <typeMapping qname="ns:MYServiceTransaction" > type="java:com.my_company_client.MYServiceTransaction" > > serializer="org.apache.axis.encoding.ser.BeanSerializerFactory" > > deserializer="org.apache.axis.encoding.ser.BeanDeserializerFactory" > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > --> > <beanMapping qname="ns:MYServiceTransaction" > languageSpecificType="java:com.my_company.client.MYServiceTransaction"/> > </service> > > According to all documentation, those two elements (typeMapping and > beanMapping) are the same if you are registering the Bean(De)serializers > (http://axis.apache.org/axis/java/user-guide.html), but that's not what I'm > finding. > > My service works with beanMapping but not with typeMapping. I need > typeMapping because I want to change the deserialization, I get a null > pointer on the BeanDeserializer. I was able to fix that but I don't want to > overwrite the BeanDeserializer.class in the axis.jar. I want to create a new > Deserializer for my objects. > > I looked at the DataSer/Deser example, but the .wsdd in that example is not > registering the (de)serializers. The example is only using a class that > serializes and deserializes without calling the WS. I tested that with my new > deserializer and that works fine, the problem is with the axis server, for > some reason the typeMapping seems not to be processed properly. > > Can you help me to fix this issue? I found emails from people in the list > with the same question, but no response. > > Thanks!! > > Marc Carrion > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
