Jitendra Kotamraju wrote:
> currently Glassfish has jax-ws 2.1.1. I do not think Glassfish or JBI is
> using Tubes(they still use Pipes !). The only tube I am aware of is
> WSIT's MEX tube. But there could be other projects that would be using
> Tubes. Also Glassfish will not take any more changes to 2.1.1
WSIT has extensive set of tubes. My understanding is that the whole
thing is built as tubes; reliable messaging, transactions, you name it.
>> We also need to do it at the right moment, too. Glassfish is getting
>> close to a release, and so it's fairly unlikely that they'll say yes
>> to this change any time soon.
>>
>> So for a while, we'll have to leave the RI as it is.
>
> Now that trunk will be readied for 2.1.2, can we consider this for 2.1.2 ??
It really all depends on what other folks say.
I also thought our current thinking is that we want 2.1.2 to be released
quickly following 2.1.1, since many of the jax-ws-commons extensions
depend on changes in that. So in that sense it's better for 2.1.2 not to
have changes that raise eyebrows.
When a change doesn't bring in a new feature nor a bug fix, it's
somewhat hard to justify at this stage of the release cycle.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com