Re: javax.xml.rpc.holders.*

From: Bjarne Rasmussen <brasmussen_at_NOVELL.COM>
Date: Mon, 09 Sep 2002 16:36:03 -0600

In the case where you go from WSDL to Java, there isn't a problem: the stub/skeleton will be configured with information about whether it's an out or in/out parameter and the runtime takes care of serializing and de-serializing the value inside the holder (and not the holder itself).

 - Bjarne.

-----Original Message-----
From: Wei Chen
Sent: 9/6/2002 5:03 PM
Subject: Re: javax.xml.rpc.holders.*

What happens if the interface is generated from WSDL that I have no
control? Basically I am obligated to implement this WSDL w/o

Another question why not making them serializable? Is there any


- Wei Chen

-----Original Message-----
From: Rasmussen, Bjarne [mailto:brasmussen_at_SILVERSTREAM.COM]
Sent: Friday, September 06, 2002 1:05 PM
Subject: Re: javax.xml.rpc.holders.*

You shouldn't use the holders when defining your remote interfaces since
can't specify whether the holder refers to an out or an in/out
Return a struct instead if your method has multiple output parameters.

 - Bjarne.

> -----Original Message-----
> From: Wei Chen [mailto:wchen_at_VITRIA.COM]
> Sent: Friday, September 06, 2002 1:02 PM
> Subject: javax.xml.rpc.holders.*
> Hi,
> I noticed that none of the Holder class are implementing
> Was that a mistake or intentional? It
> seems preventing me from using Holders to define a SEI that
> compliant with JAX-PRC 5.4.2, e.g. defining a WS view
> according to EJB 2.1 spec.
> Thanks.
> - Wei Chen