I understand the SOAP serialization should be fine.
What I concern about is the section 5.4.2 of JAX-RPC spec, where says that JAX-RPC value types must implement java.io.Serializable if Java serialization requires. Similarly in section 7.11.9 of EJB2.1 draft spec.
In particular, I can not use holders classes since Java serialization is required in my environment, in which , given a Remote interface, I would like to switch between RMI or SOAP transparently to the end users.
In general, it is somewhat confusing that JAX-RPC allows the user to define a SEI than extends java.rmi.RemoteException but doesn't have to follow other RMI rules. IMO, it would be nice at least all base type of JAX-RPC value types are compliant with Java serialization rules.
Thanks.
- Wei Chen
-----Original Message-----
From: Bjarne Rasmussen [mailto:brasmussen_at_NOVELL.COM]
Sent: Monday, September 09, 2002 3:36 PM
To: JAXRPC-INTEREST_at_JAVA.SUN.COM
Subject: Re: javax.xml.rpc.holders.*
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
To: JAXRPC-INTEREST_at_JAVA.SUN.COM
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
modification.
Another question why not making them serializable? Is there any
drawbacks?
Thanks.
- Wei Chen
-----Original Message-----
From: Rasmussen, Bjarne [mailto:brasmussen_at_SILVERSTREAM.COM]
Sent: Friday, September 06, 2002 1:05 PM
To: JAXRPC-INTEREST_at_JAVA.SUN.COM
Subject: Re: javax.xml.rpc.holders.*
You shouldn't use the holders when defining your remote interfaces since
you
can't specify whether the holder refers to an out or an in/out
parameter.
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
> To: JAXRPC-INTEREST_at_JAVA.SUN.COM
> Subject: javax.xml.rpc.holders.*
>
>
> Hi,
>
> I noticed that none of the Holder class are implementing
> java.io.Serializable. 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