day, July 26, 2003 4:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: accessing the TypeMappingRegistry in a JAXRPC
> implemenation
>
>
> > Actually, I think the empty interfaces are not the problem.
> It seems to
> me that they are just marker interfaces for subclassing w
ttp://jcp.org/en/jsr/detail?id=224
- Rob
> -Original Message-
> From: Robert Lowe [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 26, 2003 3:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: accessing the TypeMappingRegistry in a JAXRPC
> implemenation
>
>
> JAX-R
> Sent: Saturday, July 26, 2003 3:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: accessing the TypeMappingRegistry in a JAXRPC
> implemenation
>
>
> JAX-RPC 1.0/1.1 defines Serializer and Deserializer
> interfaces. However,
> both are empty except for a getMechanismType() met
nne Thomas Manes" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 26, 2003 8:50 PM
Subject: Re: accessing the TypeMappingRegistry in a JAXRPC implemenation
> Mark,
>
> I don't believe that the JAX-RPC spec defines a standard way to do custom
> [de
Mark,
I don't believe that the JAX-RPC spec defines a standard way to do custom
[de]serialization. The Axis classes are used by many vendors (IBM, Borland,
Macromedia, Pramati, etc), but I wouldn't say that it has been established
as a defacto standard. There are lots of other implementations that
