Re: is there an advantage of using axis on client side instead of jax rpc?

[Anne Thomas Manes]

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

On 11/4/05, Soactive Inc <[EMAIL PROTECTED]> wrote:

In general, both API currently have comparable functionality on the client side. Given the amount of Web Services-related activities and APIs being developed (broadly) as part of the the Axis Project (WS-Security -> WSS4J, WS-RM -> Sandesha, etc.) I would like to stick with Axis and the Apache WS API for the foreseeable future.

That said, these are all implementations of standards and as time goes on they will become more and more interchangeable in case you want to switch the underlying implementations in your architecture.

-Arun

On 11/4/05, SOA Work < [EMAIL PROTECTED]> wrote:

Hi,

I`m wondering which are the advantages of using axis on client side instead of the core jax rpc?

I think no real dynamic invocation is easily possible on both and jax rpc can generate java classes for a wsdl file too.

thx in advance

Dominik

Verschicken Sie romantische, coole und witzige Bilder per SMS!    Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193