aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Problem with Custom (De)Serializers with AXIS, WebSphere, EJB Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Problem with Custom (De)Serializers with AXIS, WebSphere, EJB" Watch "Problem with Custom (De)Serializers with AXIS, WebSphere, EJB" New topic
Author

Problem with Custom (De)Serializers with AXIS, WebSphere, EJB

Rr Kumaran
Ranch Hand

Joined: Sep 17, 2001
Posts: 548
Hi All,


Environment
------------
1. WSAD 5.1.2
2. AXIS 1.2 RC2 on both server and client
3. WebSphere Application Server 5.0
4. custom (de)serializers written replacing axis default (de)serializers both at server side and client side

I have deployed an EJB using WSAD 5.1.2's WebSphere 5.0 Test Environment and exposed it as web service using AXIS 1.2 RC2 on the server side.

I am able to test and run the ejb using WSAD's Universal Test Client but when I write a web service client program that uses AXIS 1.2 RC2 generated stubs along with custom (De)Serializer class and thier registration on the client side before invking the web service and I am getting valid soap request and below soap response from the server and I assume that
this error is coming from server side with few log stack trace like "UNABLE TO INSTANTIATE CUSTOM (DE)SERIALIZER INSTANCES"

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXException: Deserializing parameter 'dce-plane-liste-request-bean': could not find deserializer for type {http://ws.myengine.com/schemas/nec}dce-plane-liste-request-bean</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>


For your information here is my server-config.wsdd on the server side :

<service name="DCEPLWS" provider="java:EJB" style="wrapped" use="literal">
<parameter name="homeInterfaceName" value="<some valid setting>"/>
<parameter name="remoteInterfaceName" value="<some valid setting>"/>
<parameter name="allowedMethods" value="<some valid setting>"/>
<parameter name="className" value="<some valid setting>"/>
<parameter name="beanJndiName" value="<some valid setting>" />
<parameter name="jndiURL" value="iiop://localhost:2809/"/>
<parameter name="jndiContextClass" value="com.ibm.websphere.naming.WsnInitialContextFactory"/>
<parameter name="wsdlPortType" value="<some valid setting>"/>
<parameter name="wsdlServicePort" value="<some valid setting>"/>
<parameter name="wsdlTargetNamespace" value="<some valid setting>"/>
<namespace><some valid setting></namespace>
<typeMapping xmlns:ns="http://ws.mycomp.com/schemas/irscee" qname="ns c-planee-list-request-bean" type="java:com.mycomp.DCPlanListRequestBean" serializer="com.mysd.RamSerializerFactory" deserializer="com.mysd.RamDeserializerFactory" encodingStyle=""></typeMapping>
<typeMapping xmlns:ns="http://ws.mycomp.com/schemas/irscee" qname="ns c-planee-list-data-bean" type="java:com.mycomp.DCPlanListDataBean" serializer="com.mysd.RamSerializerFactory" deserializer="RamDeserializerFactory" encodingStyle=""></typeMapping>
<typeMapping xmlns:ns="http://ws.mycomp.com/wsdl/irscee" qname="ns:MyException" type="java:com.mycomp.MyException" serializer="com.mysd.RamSerializerFactory" deserializer="RamDeserializerFactory" encodingStyle=""></typeMapping>
</service>



I see that all my entries in my above server-config.wsdd file are correct. How do I further debug this problem ?

Can anyone please tell why is this error occurring and how to solve it ?




Thanks & Regards,


RR Kumaran
SCJP 1.4
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Problem with Custom (De)Serializers with AXIS, WebSphere, EJB