incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie ONeil <>
Subject a beehive release and the JSR 181 TCK issue
Date Sun, 29 May 2005 12:21:32 GMT

  There has been some confusion publicly and privately about the JSR
181 TCK issues and the WSM part of Beehive.

  The goals of WSM are to implement the JSR 181 specification and to
provide a generic annotation processor for the 181 annotations.  In
addition, there is a layer that implements JSR 181 features for the
Axis web service stack.

  The JSR 181 specification is being developed under the JCP 2.6
process and has reached the "Final Approval Ballot" stage.  But, this
is not the *final* release of the specification.  This means that the
spec is not completely finished and that the RI and TCK are not

  Both Craig and Geir have confirmed that in order to ship a "final"
version of Beehive that claims to implement JSR 181, we must pass the
JSR 181 TCK.  Currently, we are blocked on even starting this work
because the TCK has not been released.  I've exchanged some mail with
Geir, and once the TCK is available, he will help us obtain it through
Apache channels and we can start the process of passing the TCK.  The
TCK work will be done at Apache under NDA.

  The implication here is that Beehive (NetUI + Controls + WSM) can
not go "final" as a whole until the TCK has been released and WSM has

  The purpose of this milestone was to provide incremental progress
toward a 1.0-final release of the stable NetUI and Controls parts of
Beehive,  Then, we'd do a subsequent Beehive release that has JSR 181
TCK compliance.

  So, it seems to me that the passing the TCK and doing a milestone
release are orthogonal until we consider doing a release that doesn't
include WSM.

  It would certainly be possible to release a version of Beehive that
had only the NetUI + Controls bits and let the WSM part continue to
bake until the TCK becomes available and is passed.  WSM could then be
included in a later release.  Thoughts about this are welcome;
honestly, I'd be fine with this approach.

  But, I do think that we should complete the current milestone
release in order to get something new out there.



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message