Hi,
Besides the WSDL schema, I think JAXM is more suitable (and powerful) in
respect to the delivering of messages. In contrary of JAXRPC, a JAXM
implementation provider guarantees the deliver of an SOAP message like
JMS do, even the client is off-line.
PS
On Wed, 2002-11-20 at 16:14, Anne Thomas Manes wrote:
> Perhaps you don't have a WSDL description of the service.
> You can't use JAX-RPC is you don't have a WSDL file.
>
> Anne
>
> > -----Original Message-----
> > From: Public discussion on JAX-RPC
> > [mailto:JAXRPC-INTEREST_at_JAVA.SUN.COM]On Behalf Of Mischa Zurke
> > Sent: Wednesday, November 20, 2002 9:57 AM
> > To: JAXRPC-INTEREST_at_JAVA.SUN.COM
> > Subject: jaxm - rpc style...what for
> >
> >
> > Hi,
> >
> > I just read that you can use JAXM to do SOAP-RPC
> > using the SOAPConnection class. As far as I understand,
> > with this approach you got to manage the whole
> > serialization/deserialization of the soap messages
> > by your own. So I just wonder why anybody should use
> > SOAP-MESSAGING to fulfill a remote method call.
> > Does anybody know a good example to justify such an
> > approach and not to use JAX-RPC?
> > Thanx,
> > Mischa
> >
--
PS
pedro-b-salazar_at_ptinovacao.pt
PGP:0E129E31D803BC61