I'll make the change.
It is related to the other change that I proposed earlier today.
The idea is that the (javaType, xmlType) information should be communicated
to the Call
object using the "full" addParameter method. This ParameterDesc
information is then
attached to RPCParam, which in turn causes the
SerializationContext.serialize() method
to be invoked with the (javaType, xmlType) information.
Thus the Stub can communicate the (javaType, xmlType) information and the
runtime will use it without doing any guessing.
Makes a lot of sense. Thanks to Glen for adding the ParameterDesc stuff
and doing a lot
of this preliminary work.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Russell Butek
To: R J Scheuerle Jr/Austin/IBM
04/05/2002 09:12 cc:
AM From: Russell Butek/Austin/IBM@IBMUS
Subject: Re: addParameter(Document
link: R J Scheuerle Jr)
It probably uses what it uses because that's all that was there when
JavaStubWriter was written. Go ahead and update it, if you like. Or I
could do it, too.
Russell Butek
[EMAIL PROTECTED]
To: Russell Butek/Austin/IBM@IBMUS
cc:
From: R J Scheuerle Jr/Austin/IBM@IBMUS
Subject: addParameter
Why is the stub using the Call.addParameter method that only sets the
xmlType (and not the javaType).
The reason that I am asking is that I am making some changes to the runtime
to use the parameter
information to invoke the context.serialize() method with the specified
(xmlType, javaType) so that
the runtime does not need to introspect or guess. And if we are using the
addParameter that doesn't
pass the javaType, the runtime still needs to do some guessing.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
