You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andy Micone (JIRA)" <ax...@ws.apache.org> on 2004/12/08 00:39:18 UTC
[jira] Created: (AXIS-1705) Problem deserializing complex array types from .NET with WSDL2Java Code
Problem deserializing complex array types from .NET with WSDL2Java Code
-----------------------------------------------------------------------
Key: AXIS-1705
URL: http://nagoya.apache.org/jira/browse/AXIS-1705
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
{http://ww.ExchangeNetwork.net/schema/v1.0/node.xsd}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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1705) Problem deserializing complex array types from .NET with WSDL2Java Code
Posted by "Andy Micone (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXIS-1705?page=history ]
Andy Micone updated AXIS-1705:
------------------------------
Attachment: cdx.wsdl
WSDL Attached
> Problem deserializing complex array types from .NET with WSDL2Java Code
> -----------------------------------------------------------------------
>
> Key: AXIS-1705
> URL: http://nagoya.apache.org/jira/browse/AXIS-1705
> 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
> {http://ww.ExchangeNetwork.net/schema/v1.0/node.xsd}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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1705) Problem deserializing complex array types from .NET with WSDL2Java Code
Posted by "Andy Micone (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXIS-1705?page=comments#action_56353 ]
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: http://nagoya.apache.org/jira/browse/AXIS-1705
> 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
> {http://ww.ExchangeNetwork.net/schema/v1.0/node.xsd}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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1705) Problem deserializing complex array types from .NET with WSDL2Java Code
Posted by "Andy Micone (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXIS-1705?page=comments#action_56400 ]
Andy Micone commented on AXIS-1705:
-----------------------------------
I discovered the cause of this bug, I'll leave it to the devs to determine what should be the correct behavior. The namespace of the supplied WSDL was listed in the namespace defined under http://www.exchangenetwork.net, the .NET client requested the NodeDocument in the namespace defined under http://www.ExchangeNetwork.net. Arguably, since domain names are case-insensitive, these namespaces should have been considered synonymous. They are not. I don't know what the standards say about this, however. In any case, its a problem with interpreting the namespace of the request.
> Problem deserializing complex array types from .NET with WSDL2Java Code
> -----------------------------------------------------------------------
>
> Key: AXIS-1705
> URL: http://nagoya.apache.org/jira/browse/AXIS-1705
> 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
> {http://ww.ExchangeNetwork.net/schema/v1.0/node.xsd}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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira