Thanks Arthur. I've corrected the example in the release notes.
Lawrence Mandel
| Arthur Ryman/Toronto/[EMAIL PROTECTED]
12/07/2005 05:02 PM
|
|
+1
I did a simple smoke test by reading a WSDL and dumping out the component model. It worked well. Nice progress.
I did notice an error in the example in the Release Notes. The line:
Description descComp = desc.getDescriptionComponent(); <-- the Description component
should be:
Description descComp = desc.toComponent(); <-- the Description component
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| Lawrence Mandel/Toronto/[EMAIL PROTECTED]
12/07/2005 12:23 AM
|
|
After reviewing the current M2 status with John, I've placed a Woden 1.0.0 M2 Candidate build at
http://cvs.apache.org/dist/ws/woden/milestones/1.0.0M2-incubating/
As can be seen, I've updated the name of the Woden archives to include incubating as per the incubator release process.
The Woden M2 candidate includes the major work items from the M2 plan. Specifically, the following items are complete in the M2 Candidate:
WSDL 2.0 Interface parsing (DOM)
Create validation framework
WSDL 2.0 Binding parsing (DOM)
WSDL 2.0 Binding extensibility mechanism (DOM)
WSDL 2.0 SOAP Binding extension (DOM)
Implement validation logic for types and Interface
Unit tests for validation logic for types and Interface
Integrate W3C WSDL 2.0 types and Interface tests into Woden test suite
The following items are incomplete in the M2 plan:
Unit tests for Interface parsing (DOM)
Create validation framework including extension mechanism
Unit tests for Binding parsing (DOM)
Unit tests for SOAP Binding extension (DOM)
Update technical documentation about Woden design and implementation on Wiki
Create initial user documentation
As can be seen from the above lists, work needs to be done on the automated unit tests for the parser and documentation. The validation tests do provide some tests for the parser and John performed manual testing to verify that the parser is functioning as expected. John and I plan on working more on documentation as more features become available in M3.
Both John and I think Woden is in good shape to declare M2 as major progress has been made on the parser and the validator. At this point we'd like to ask the Woden committers to vote on the status of M2. John and I both vote +1 (so +2). Please vote ASAP. We will collect votes until EOD Wednesday, Dec. 7. If there are no negative votes I will then request Incubator PMC approval to release M2. Once the PMC approves, M2 will be declared and a link will be placed on the Woden site. (Feel free to reply to this note with any concerns over this process.)
Thanks,
Lawrence Mandel
