An interface is a lifetime commitment :-)
Staying with the status quo might be best.
Sean
On Fri, May 30, 2008 at 12:22 PM, Marc Hadley <Marc.Hadley_at_sun.com> wrote:
> On May 30, 2008, at 1:37 PM, Bill Burke wrote:
>>
>> As far as JAX-WS goes, I don't think it should even be mentioned in the
>> specification. The Endpoint interface brings in a lot of baggage that we
>> don't want/need in REST, or concepts (like Handlers) that we may want a
>> JAX-RS style/flavor for.
>>
> Having looked more closely at JAX-WS endpoint I have to agree that we should
> steer clear, there's too much that's inappropriate.
>
> So, the question is: do we invent our own interface similar to JAX-WS
> Endpoint but without the stuff we don't need or do we stick with the current
> API and defer the question of a standard endpoint interface to a subsequent
> revision of the spec.
>
> Personally I'm happy with the status quo.
>
> Marc.
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: users-help_at_jsr311.dev.java.net
>
>