A new version of WSDL4J, v1.6, is due out next week to support a
maintenence release of JSR110. I just wanted to make sure the
axis-dev community is aware of this and can perhaps think about if/when
to use it in Axis2. If any of you subscribe to the WSDL4J mailing
list, you should already be aware of this.
The original WSDL4J postings are below.
Functional enhancements are described in the JSR110 maint rel Change
Log which you can download from http://sourceforge.net/projects/wsdl4j/. Link to the "Files" page, then under package JWSDL Maintenance Release 1.2 see the file: JSR110_JWSDL12_MRChangeLog_Proposed.pdf.
Apart from resolving outstanding Sourceforge WSDL4J bug trackers, other
content of the v1.6 release that might interest you includes SOAP 1.2
binding extensions and relaxing the extensibility rules to comply with
WS-I BP 1.1 in support of JAX-WS (i.e. any WSDL element can now have
extension attributes or extension elements).
regards,
John Kaputin (JSR110/WSDL4J maint lead).
----- Forwarded by John Kaputin/UK/IBM on 24/08/2006 12:34 -----
John
Kaputin/UK/IBM
To
04/08/2006
16:50 [EMAIL PROTECTED]
cc
Subject
Fw: JSR110 Maintenance Release of
JWSDL/WSDL4J
The JSR110 maintenance release was announced by the JCP PMO on 25th July.
The review period for the Change Log will complete on 28th August (see
previous posting below for details to access the Change Log). The JWSDL API
will move to v1.2, supported by reference implementation WSDL4J v1.6.
WSDL4J Sourceforge CVS now has a branch called 'wsdl4j-1_6-dev' to which
the code changes for the maintenance release will be added. This should be
done by early next week. These code changes are for outstanding
enhancements/bug fixes that modify the JWSDL API. These changes are
proposed in the Change Log. Each proposed change also has a Tracker item
open on the Sourceforge WSDL4J project.
You can add comments to the Tracker or post to this mailing list.
All outstanding enhancements and bug fixes that DO NOT change the JWSDL API
have now been committed to SourceForge CVS HEAD. I will create a WSDL4J
v1.53 release from HEAD prior to concluding the maintenance release on 28th
August and merging the wsdl4j-1_6-dev branch back into HEAD. v1.53 will
roll-up fixes applied since the v1.52 release and will be the final release
of WSDL4J at the current JWSDL v1.1 API level.
regards,
John Kaputin
----- Forwarded by John Kaputin/UK/IBM on 04/08/2006 16:30 -----
John
Kaputin/UK/IBM
To
22/07/2006
02:35 [EMAIL PROTECTED]
cc
Subject
JSR110 Maintenance Release of
JWSDL/WSDL4J
There are several outstanding issues and Tracker items against WSDL4J that
require modification of the JWSDL API specified by JSR110. This requires a
Maintenance Release of JSR110, as defined by the JCP
2.1 process. The last
such maintenance release was January 2005, which moved the JWSDL API to
v1.1 and its Reference Implementation to WSDL4J v1.5. The new maintenance
release will define JWSDL 1.2 with the R/I provided by WSDL4J
1.6.
I have captured the requirements as proposed changes in a Change Log
document and uploaded it to the SourceForge WSDL4J project at
http://sourceforge.net/projects/wsdl4j/
. Link to the "Files" page, then
under package JWSDL Maintenance Release 1.2 see the file:
JSR110_JWSDL12_MRChangeLog_Proposed.pdf.
I have also requested the JCP to update the JSR110 web pages to formally
announce the Maintenance Review.
Please review the changes proposed in this document and the associated
Tracker items during the 30 day Maintenance Review period and post your
comments/feedback/suggestions to this mailing list or as comments on the
Tracker items.
I hope to complete the Maintenance Review by 23rd August. During this
period I will create a CVS branch "wsdl4j16" from CVS HEAD and commit the
required code changes to it for you to review and try out. Feedback will be
incorporated into this branch. At completion of the review, this branch
will be merged back to CVS HEAD and WSDL4J 1.6 will be released.
Note, there are also some pending bug fixes or enhancements that do not
affect the API. I expect to make a WSDL4J 1.53 release to roll up these
fixes and any previous fixes since v1.52. These fixes will also be included
in v1.6.
regards,
John Kaputin
