JAX-RPC and JSR-109 support both RPC and Document style services, but both
APIs are designed to support an RMI-style programming interface -- meaning
that the JAX-RPC runtime performs automatic marshalling and unmarshalling
of SOAP messages -- automatically converting Java objects to XML and vice
versa. If you prefer to build XML-oriented applications then you probably
want to use JAXM rather than JAX-RPC.
Anne
At 04:55 AM 1/23/2004, you wrote:
>Thanks for the information Anne. Now I get a better idea of what JSR-109
>is. It seems like a pretty useful specification.
>
>I understand that JSR-109 doesn't force you to use EJBs, you can have a
>servlet implementation or an EJB implementation in a JSR-109 web service,
>which is great. But I still get the impression that it forces you to use a
>procedure-oriented model for building web services. Is it possible to
>build document-oriented web services using JSR-109?
>
>Thanks,
>Mete
>
>---------- Original Message ----------------------------------
>From: Anne Thomas Manes <anne_at_manes.net>
>Reply-To: users_at_jax-rpc.dev.java.net
>Date: Fri, 23 Jan 2004 18:12:56 +0100
>
> >Mete,
> >
> >The JAX-RPC spec defines a framework for Web services that can work in a
> >variety of Java environments -- including J2SE, Servlet engines, and J2EE.
> >But it provides a complete specification only for the servlet-based
> >environment. JSR-109 provides the complete specification for JAX-RPC in a
> >J2EE environment. It doesn't require that you use EJBs, but it does specify
> >how to map JAX-RPC to EJBs. I think that the most critical extra value of
> >JSR-109 over plain JAX-RPC is that it defines a standard deployment
> >descriptor for Web services.
> >
> >Anne
> >
> >At 10:36 AM 1/23/2004, you wrote:
> >>Hello,
> >>
> >>I read the JSR-109 JSR page and I kind of get the impression that JSR-109
> >>suggests a framework for building web services. JAX-RPC is also a
> >>framework for building web services but I get the impression that Jsr-109
> >>is a superset of JAX-RPC. One thing that confuses me is whether JSR-109
> >>forces the use of EJBs. It is not clear from the JSR page. Can any of you
> >>help me with these questions.
> >>
> >>1) What really is JSR-109? Can someone give a better explanation than the
> >>one found on the JSR page?
> >>
> >>2) Does JSR-109 force the use of EJBs in web service development? Can I
> >>use JSR-109 without using EJBs?
> >>
> >>3) What are the advantages of using JSR-109 compared with just using
> >>JAX-RPC alone? What does JSR-109 buy me on top of JAX-RPC?
> >>
> >>Thanks,
> >>Mete
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> >>For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> >For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
>For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
~~~~~~~~~~~~~~~~~~
Anne Thomas Manes
VP & Research Director
Burton Group
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net