Will the JAX-RPC 1.1 SI/RI implement the deployment model described in
Web Services for J2EE 1.1 specification (JSR-109)?
> -----Original Message-----
> From: Doug Kohlert [mailto:Doug.Kohlert_at_Sun.COM]
> Sent: Wednesday, July 23, 2003 12:47 PM
> To: Mark D. Hansen
> Subject: Re: Plugging JAXB into JAXRPC via the Extensible
> Type Mapping /
> Serialization Framework ?
>
>
> Mark,
> We are releasing the FCS version of JAXRPC 1.1 in I think October as
> part of the J2EE 1.4 release. It should be fixed then. Sorry for the
> issues.
>
> Mark D. Hansen wrote:
> > Doug,
> >
> > OK - thanks for your help. I was trying to use rpc/enc
> because I discovered (in an earlier thread) that the current
> RI doesn't support dynamic proxy for oneway doc/lit.
> >
> > I'm trying to use JAX-RPC as a platform to develop a simple
> messaging framework. JAXM would actually be better suited to
> my purposes, but I can't use JAXM because I need to use
> official J2EE technology. I think that I'm going to have to
> give up on trying to do this with the current RI because of
> the lack of dynamic proxy client support for oneway doc/lit.
> >
> > Maybe I should try using a different JAX-RPC implementation
> and come back to the RI at the next release? Any suggestions
> are welcome.
> >
> > -- Mark
>
>
> --
> Doug Kohlert
> Java Software Division
> Sun Microsystems, Inc.
> phone: 503 345-9806
>