xsi:nil="true" and anyType deserialization
Hey folks,
So, changing the WSDL didn't improve things for us (we still send the
xsi:nil="true" attribute). Upon further testing, I've also discovered
that this same issue essentially is causing the "could not find
deserializer ... anyType" exceptions that a lot of us are seeing. Here
is a suggestion though. This bug seems confined to createResource (I'm
guessing) because it is the only one that takes an empty parameter list.
Since our purpose here isn't to test the interoperability of the
interop. factory port type, but rather the ByteIO stuff after creating
the resource, can we maybe just agree to change the createResource
element type to have a dummy parameter in it. For example, can we
change the message type to have the following XML definitions:
I'm all in for this! Cheers, Michel Mark Morgan wrote:
Hey folks,
So, changing the WSDL didn't improve things for us (we still send the xsi:nil="true" attribute). Upon further testing, I've also discovered that this same issue essentially is causing the "could not find deserializer ... anyType" exceptions that a lot of us are seeing. Here is a suggestion though. This bug seems confined to createResource (I'm guessing) because it is the only one that takes an empty parameter list. Since our purpose here isn't to test the interoperability of the interop. factory port type, but rather the ByteIO stuff after creating the resource, can we maybe just agree to change the createResource element type to have a dummy parameter in it. For example, can we change the message type to have the following XML definitions:
I believe that this would fix, or at least aid in fixing MOST of our problems so far.
-Mark and Karolina
-- byteio-wg mailing list byteio-wg@ogf.org http://www.ogf.org/mailman/listinfo/byteio-wg
It is fine with me too.
On 7/25/07, Mark Morgan
Hey folks,
So, changing the WSDL didn't improve things for us (we still send the xsi:nil="true" attribute). Upon further testing, I've also discovered that this same issue essentially is causing the "could not find deserializer ... anyType" exceptions that a lot of us are seeing. Here is a suggestion though. This bug seems confined to createResource (I'm guessing) because it is the only one that takes an empty parameter list. Since our purpose here isn't to test the interoperability of the interop. factory port type, but rather the ByteIO stuff after creating the resource, can we maybe just agree to change the createResource element type to have a dummy parameter in it. For example, can we change the message type to have the following XML definitions:
I believe that this would fix, or at least aid in fixing MOST of our problems so far.
-Mark and Karolina
-- byteio-wg mailing list byteio-wg@ogf.org http://www.ogf.org/mailman/listinfo/byteio-wg
-- ------------------------------------------------------------------------ Mohammad Shahbaz Memon Department of Applied Mathematics Forschungszentrum Jülich GmbH Jülich Germany Skype: m.memon Web page: http://www.fz-juelich.de/zam/ZAMPeople/memon_m Office: +49 (0)2461 61 6567 Fax: +49 (0)2461 61 6656
participants (3)
-
Mark Morgan -
Michel Drescher -
Mohammad Shahbaz Memon