I believe the developers plan to implement support for JAX-RPC 1.1 on top of Axis 2 -- especially if the user community wants it.
Anne
On 11/8/05, Guy Rixon <[EMAIL PROTECTED]> wrote:
Anne,
is there a policy for how long Axis will continue to support JAX-RPC 1.1?
Cheers,
guy
On Tue, 8 Nov 2005, Anne Thomas Manes wrote:
> In anwser to Toby's question:
>
> JAX-RPC is a standard Java API. As with other standard Java APIs ( e.g.,
> JDBC, JMS, Servlet, EJB, etc), many different vendors and open source
> projects can implement the API.
>
> Axis is a web services platform that implements the JAX-RPC 1.1 API
> specification.
>
> Sun leads the JAX-RPC and JAX-WS JCP expert groups, and therefore controls
> the future of these APIs. I've never been a fan of JAX-RPC. Although JAX-WS
> is a significant improvement over JAX-RPC, I still think it has a number of
> flaws--in particular, it's still too focused on making SOAP look like RMI.
>
> In answer to Phil's question:
>
> Applications implemented using the JAX-RPC 1.1 API are fully-functional web
> services applications -- whether or not the API changes at some point down
> the road. There's no need to update these applications just because a new
> release of the API is released. (I suspect many of you are still running
> apps that use older versions of EJB, Servlet, JSP, JMS, etc. And a few of
> you probably also have apps written using Apache SOAP. As long as they're
> still working, there's no need to upgrade them.)
>
> Axis 1 was designed based on the JAX-RPC spec. (And I think this design
> center severely constrains the capabilities of the system. JAX-RPC was much
> too centered on the RPC/encoded style.) Converting Axis 1 to JAX-WS would
> probably require a significant, if not complete, re-write. It doesn't make
> sense to do that in light of Axis 2.
>
> Axis 2 was not designed based on any API. Instead the team started from
> scratch with a goal to design an extensible system that supports the
> extended web services framework. With a solid, extensible model at its core,
> Axis can support any API on top of that model. Therefore Axis 2 will be able
> to support both JAX-RPC and JAX-WS.
>
> As a developer building production-class applications today, you really
> don't have the luxury of using pre-beta software. Both Axis 2 and Sun's
> JAX-WS products are pre-beta, therefore you probably can't use either.
> Choosing between Axis 1 and Sun's JAX-RPC implementation, I recommend Axis
> 1.
>
> If you aren't building production-class applications, then you do have the
> luxury of using pre-beta software, in which case I recommend experimenting
> with both Axis 2 and JAX-WS. Be aware, though, that the JAX-WS specification
> has not yet been finalized, therefore the API may change in the future.
>
> Personally, I prefer the Axis 2 approach -- base the product on an
> extensible model (AXIOM), and build APIs on top of that model. But I know a
> number of folks that I have great respect for that prefer JAX-WS.
>
> Anne
>
> On 11/8/05, Weston, Toby < [EMAIL PROTECTED]> wrote:
> >
> > Hi Folks,
> >
> > I'm a bit confused about the relationship between Axis and JAX-RPC, can
> > someone outline it please?
> >
> > As background; http://forum.java.sun.com/thread.jspa?threadID=679469
> >
> > Thanks in advance,
> > Toby
> >
> > -----Original Message-----
> > From: Gonia, Philip T [mailto:[EMAIL PROTECTED]]
> > Sent: 07 November 2005 22:10
> > To: [email protected]
> > Subject: Re: is there an advantage of using axis on client side instead of
> > jax rpc?
> >
> > Sorry about the last post it was an accident.
> >
> > Anne, in your view, how does this impact current Axis application
> > development. Are current Axis aware
> > applications obsolete even before they are released at this point?
> >
> > Phil
> >
> > On Nov 6, 2005, at 12:49 AM, Anne Thomas Manes wrote:
> >
> > > One note: the next release of JAX-RPC (which is currently in public
> > > review) is so different from the last release that Sun changed its
> > > name to JAX-WS. This new version relies on Java 5 and makes extensive
> > > use of metadata annotations. The programming model is completely
> > > different.
> > >
> > > Given that JAX-RPC will be deprecated soon, I don't think it matters
> > > which client you use in terms of long-term protection -- all current
> > > implementations will be obsolete. But as Arun says, the Axis team is
> > > building much more extensive support for the advanced WS-* specs.
> > >
> > > Anne
> >
>
Guy Rixon [EMAIL PROTECTED]
Institute of Astronomy Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
