axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Micone (JIRA)" <>
Subject [jira] Commented: (AXIS-1705) Problem deserializing complex array types from .NET with WSDL2Java Code
Date Tue, 07 Dec 2004 23:50:15 GMT
     [ ]
Andy Micone commented on AXIS-1705:

I would be happy to provide a fix for this issue if someone could give me some pointers to
how to fix the code.

> Problem deserializing complex array types from .NET with WSDL2Java Code
> -----------------------------------------------------------------------
>          Key: AXIS-1705
>          URL:
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization, WSDL processing
>     Versions: current (nightly)
>  Environment: RHEL9, J2SDK1.4.2_04, Tomcat 5.5.5 with Compatibility, Axis Nightly (CVS)
>     Reporter: Andy Micone
>  Attachments: cdx.wsdl
> A provided WSDL expects an inbound request to consist of an array of a complex type made
up of simple primitives. .NET validation client accessing service reports org.xml.sax.SAXException:
No deserializer defined for array type
> {}NodeDocument returned from Axis server.
To simulate:
> 1) Start fresh, compile nightly, install tomcat with compatibility package, install activation.jar
and mail.jar.
> 2) Using nightly build use WSDL2Java to generate all stubs, binding implementation, and
deploy.wsdd and compile the class files.
> 3) Make the distribution and copy the axis webapps folder into tomcat.
> 4) Copy the WSDL2Java generated classes into the WEB-INF/classes directory.
> 5) Deploy the service with the WSDL2Java generated deploy.wsdd.
> 6) Attempt to have a .NET client initiate and inbound request with the type in question.

> Axis will generate a no deserializer error. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message