hi guys,
 
i'd like to point out that this particular problem is a direct result of the
current JAX/RPC specification. basically, if you define an argument as
a holder type on the server, it is ambiguous whether it's intended to be
an out or an inout holder.
 
i've emailed a suggestion through many channels that JAX/RPC
adopts an approach where there is an OutHolder and InOutHolder for
each data type, thereby providing a clear, unambiguous binding from
both a client and a server perspective.
 
unfortunately, i have received no feedback whatsoever on this suggestion.
i only hope that this problem is addressed before the 1.0 specification is
released so that the java community does not have to live with an
unnecessary additional level of complexity.
 
cheers,
graham
-----Original Message-----
From: Chris Ruegger [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 4:04 PM
To: [EMAIL PROTECTED]
Subject: setting up output parm

I'm trying to write a webservice that has an input/output String parmeters. In my Java code
I'm declaring the parameter as a StringHolder. What do I need to put in my .wsdd file
when I deploy the service? Is this documented anywhere where I can read on how to
set up input/output params in general? The Axis user guide is quite sparse with
specific details and I don't see this in any of the examples.
Thanks
 

Reply via email to