Bug 3483 – xsd:anyType not serialized correctly

Bug 3483 - xsd:anyType not serialized correctly

Summary:

xsd:anyType not serialized correctly

Status:	NEW

Product:	Java WS Core
Component:	globus_wsrf_core
Version:	4.0.0
Platform:	PC Linux

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Rachana Ananthakrishnan

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-14 17:12 by Shishir Bharathi
Modified:	2008-03-28 06:18 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Shishir Bharathi 2005-06-14 17:12:45

xsd:anyType elements are sent over the wire as of type
{http://www.globus.org/foobar}QueryExpressionDialect.

Definition:
<xsd:complexType name="messageType">
   <xsd:sequence>
       <xsd:element name="type" type="tns:descriptorType"/>
       <xsd:element name="messageID" type="xsd:string"/>
       <xsd:element name="referenceID" type="xsd:string" nillable="true"/>
       <xsd:element name="payload" type="xsd:anyType" nillable="true"/>
   </xsd:sequence>
</xsd:complexType>

SOAP: (Client sets a java.lang.String object as payload)
<message xmlns="http://www.globus.org/namespaces/2005/06/WSPeer">
    <type xmlns="">CONNECT</type>
    <messageID xmlns="">56E8D9E0-DD16-11D9-B964-D3DC482A8318</messageID>
    <referenceID xsi:nil="true" xmlns=""/>
    <payload xsi:type="ns1:QueryExpressionDialect" xmlns=""
xmlns:ns1="http://www.globus.org/foobar">HELLO WORLD</payload>
</message>

This results in an exception:
<faultstring>org.xml.sax.SAXException: No deserializer for
{http://www.globus.org/foobar}QueryExpressionDialect</faultstring>

Temporary workaround (gawor@mcs.anl.gov) is to remove the mapping for
QueryExpressionDialect from $GLOBUS_LOCATION/client-config.wsdd. But, this
mapping is used by other services.

------- Comment #1 From Charles Bacon 2007-09-12 16:40:42 -------

Reassigning to current wsrf developer to close/fix as appropriate

------- Comment #2 From Roland Kuebert 2008-03-28 06:18:14 -------

Changing the $GLOBUS_LOCATION/client-config.wsdd did not work for me, but
removing the mapping from
$GLOBUS_LOCATION/etc/globus_wsrf_core/server-config.wsdd did the trick.