I have a problem with a complex type going into and out of a SOAP routine in that it
will not deserialize the resulting structure.
The setup is ..
I have a structure - DISPLAYCONTEXT that is send to a rpc service. This service
returns another structure, ELEMENT, that contains a DISPLAYCONTEXT structure. So in
effect I have
DISPLAYCONTEXT { int x; int y; } (as the input parameter)
ELEMENT { int z; String s; DISPLAYCONTEXT dc; } (as the output parameter)
They are both configured as JavaBeans.
The problem is in mapping the types in the call. If i map the DISPLAYCONTEXT and the
returned 'dc' using SMR.mapTypes(), both as beans, then the SOAP client complains that
it there is no deserializer for 'dc'. If i try any other way of mapping them i get the
same message. Note it doesnt work if i only map it once as a bean.
It seems that you can only map ONE class per call. i.e. i require to map the same
class twice (one for the output and one for the input), but the mapping registry will
only look for one and ignore the other causing an error on deserialization.
Is there a correct way of mapping this ... or is it a bug in SOAP 2.3.1 ??
MS SDK v3 returns a correct XML response.
Client is Apache SOAP 3.2.1, Server is MS SDK v3 (untyped).
rgds
Ian Minshall
I
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
