The issue is to not change the RI API around Tubes (used in Glassfish as
well as other places). I have done some work on this and sent it to
Kohsuke. It does look like it should be possible to do this (an issue or
2 to resolve).
If it proves not to be possible then a parallel generic tubes project
that the RI does not use would still be nice.
Pete
Marek Potociar wrote:
> Kohsuke Kawaguchi wrote:
>> I see. I guess it never occurred to us, but now that you mentioned
>> it, it could have been a library on its own.
>>
>> We can have a spin-off library that does just that, but I think at
>> this point it's fairly difficult for the JAX-WS RI to switch to using
>> that library, because this is a part of the externally visible API,
>> and a lot of code has already been written internally/externally to
>> rely on it. A package name change would be disastrous.
> Hi Kohsuke,
>
> what Pete suggests sounds like an interesting idea to me. I am not
> sure how many cycles could you guys spend on this, but in the first
> phase you could create the generic library and modify existing classes
> to serve as wrappers. Later you could refactor the RI to use the
> generic library directly.
>
> Marek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>