Status and direction
by Thomas Diesler
Hi Folks,
please read this to the end - there is something todo for you. Merci.
We recently released
jbossws-1.2.1.GA 15-Apr (to the community)
jbossws-2.0.0.CR5 19-Apr (only to the repository)
both releases were cut from trunk only a few days in between. As you
might have seen on core jbossws-2.0.0.CR5 is our fully JavaEE5 certified
stack - jbossws-1.2.1.GA is some minor issues short of that. Its a
little unfortunate that we missed the jboss-4.0.2.GA by those four days,
but then again we were never aiming at JavaEE5 compliance with jboss-4.2.x
Following our 8 week release cycle, jbossws-2.0.0.GA is targeted for
1-Jul-2007 (giving some way for the lazy May). It will include some
outstanding bug fixes and stuff that comes up with the two releases above.
Concurrently we'll be working on general web service integration layers
for JBossAS and the ESB platform. We want to achieve plugability for
webservice implementations paving the way to run the Sun RI as an
alternative web service stack in both platforms. This is necessary
because we want to leverage the much needed WS-* funtionality from
project Tango (https://wsit.dev.java.net/specification-links.html)
This work will continue on trunk and be part of a future jbossws-2.1.0
release. We distribute our effort like this
jbossws-2.0.x 40%
jbossws-2.1.x 60%
Between now and code freeze for jbossws-2.0.0.GA (18-Jun-2007) we have
roughly 40 working days, 16 of which should be spent on jbossws-2.0.0. I
calculate 1.5 issues per day, which leads to about 24 issues that could
be resolved in that time frame.
Please let me know how many workdays you can *actually* dedicate to
jbossws-2.0.0 until code freeze? The good people from support obviously
have much less than 40 wd on the other hand they can dedicate all their
dev time to jbossws-2.0.0
workdays dedicated for jbossws-2.0.0 until code freeze (18-Jun-2007)
--------------------------------------------------------------------
Thomas: 12
Heiko:
Darran:
Magesh:
David:
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years
JBWS-1133
by Darran Lofthouse
Does anyone have any objections to these changes being committed for
deployment using JBoss 4.0.x and 4.2.x: -
http://jira.jboss.com/jira/browse/JBWS-1133
Basically additional information is read from the web.xml to cope with
exploded deployments that are being deployed a second time.
This is not a problem with JBoss 5 so these changes are just required in
the integration layer for 4.0.x and 4.2.x.
If not I will close the issue as 'Wont Fix'.
Regards,
Darran Lofthouse.
17 years
Hudson Builds
by Darran Lofthouse
Is there a mailing list I can subscribe to to receive notifications from
the Hudson builds?
Regards,
Darran Lofthouse.
17 years
Which branch for JBossWS 1.2.2?
by Darran Lofthouse
Which branch should be used for JBossWS 1.2.2?
Can these just go to trunk or is 1.2.2 going to continue from the 1.2.1
branch after it is released?
Regards,
Darran Lofthouse.
17 years
Fw: [members] Approval of Web Services Transaction Version 1.1 as an OASIS Standard
by Heiko Braun
Begin forwarded message:
Date: Mon, 16 Apr 2007 14:39:49 -0700
From: "Mary McRae" <mary.mcrae(a)oasis-open.org>
To: <members(a)lists.oasis-open.org>, <tc-announce(a)lists.oasis-open.org>
Cc: <ws-tx(a)lists.oasis-open.org>
Subject: [members] Approval of Web Services Transaction Version 1.1 as
an OASIS Standard
To OASIS members:
The ballot for approval of Web Services Transaction Version 1.1 as
OASIS Standard, announced at [1], was completed with sufficient
affirmative votes to approve the specification. However, because there
were negative votes, the Web Services Transaction (WS-TX) Technical
Committee was required to decide how to proceed, per the OASIS TC
Process (at [2]). The TC gave consideration to the negative votes but
has voted to request the specification be approved. (See [3].)
We are pleased, therefore, to announce that Web Services
Transaction Version 1.1 has been approved as an OASIS Standard. The
submission of the approved standard can be found at [4].
Congratulations to the TC, and the community of implementers,
developers and users who have brought the work successfully to
culmination.
Mary
---------------------------------------------------
Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae(a)oasis-open.org
web: www.oasis-open.org
[1]
http://lists.oasis-open.org/archives/tc-announce/200703/msg00017.html
[2] http://www.oasis-open.org/committees/process.php#3.4 [3]
http://www.oasis-open.org/committees/ballot.php?id=1269 [4]
http://lists.oasis-open.org/archives/tc-announce/200703/msg00005.html
---------------------------------------------------------------------
This email list is used solely by OASIS for official consortium
communications.
Opt-out requests may be sent to member-services(a)oasis-open.org,
however, all members are strongly encouraged to maintain a subscription
to this list.
17 years
