PROPOSAL: ServiceClient

[Glen Daniels <gd...@macromedia.com>]

I've heard rumors that the ServiceClient class is going to go away.  I'd
like to suggest how exactly we handle that.

There are a lot of docs, including at least the Axis docs, the book that
Doug and I are involved in, and the JRun Web Services tech preview, which
reference the ServiceClient APIs.  Not to mention a lot of code people have
potentially been writing to the API.

So rather than removing the class, I'd like to mark it deprecated and leave
its API unchanged.  The implementation should become a simple delegation to
Call.  That way current users can still use ServiceClient, and we can remove
it entirely after a few releases....

What say y'all?

--G

Re: PROPOSAL: ServiceClient

[Ravi Kumar <rk...@borland.com>]

Though I would rather not have 2 ways of doing the same thing in an alpha
product, there seems to be valid reasons to let it be, albiet deprecated.

+1

Another thought:
Wouldn't it be worthwhile refactoring ServiceClient to extend from
org.apache.axis.rpc  (aka javax.xml.rpc)?

Ravi

Glen Daniels wrote:

> I've heard rumors that the ServiceClient class is going to go away.  I'd
> like to suggest how exactly we handle that.
>
> There are a lot of docs, including at least the Axis docs, the book that
> Doug and I are involved in, and the JRun Web Services tech preview, which
> reference the ServiceClient APIs.  Not to mention a lot of code people have
> potentially been writing to the API.
>
> So rather than removing the class, I'd like to mark it deprecated and leave
> its API unchanged.  The implementation should become a simple delegation to
> Call.  That way current users can still use ServiceClient, and we can remove
> it entirely after a few releases....
>
> What say y'all?
>
> --G