+1 On 6/12/06, John Kaputin <[EMAIL PROTECTED]> wrote:
> BTW, what do you mean by vote via the builds page?I guess this is a punctuation problem. I meant to 'vote' (the action) to 'release M5 via the builds page' (subject). Drop the comma? Woden committers please vote to release this build as the Milestone 5 release, via the builds page on the Woden website John Kaputin "Arthur Ryman" <[EMAIL PROTECTED] il.com> To [email protected] 11/06/2006 02:01 cc Subject Please respond to Re: [vote] Woden M5 Release [EMAIL PROTECTED] he.org +1 I've been using the code extensively on the W3C test suite. The current failures are mainly due to a lack of clarity concerning REQUIRED extension properties and this is being resolved. BTW, what do you mean by vote via the builds page? On 6/10/06, John Kaputin <[EMAIL PROTECTED]> wrote: > > I have placed the M5 candidate build at: > http://people.apache.org/dist/ws/woden/milestones/1.0.0M5-incubating/ > > Woden committers please vote to release this build as the Milestone 5 > release, via the builds page on the Woden website: > http://incubator.apache.org/woden/dev/1.0/builds.html > > In accordance with the Apache process, votes should be returned within 72 > hours (by Wed June 14th 2006, 8pm US EST). > > The Woden M5 candidate includes major work items from the Milestone 5 plan, > which can be viewed at: > http://incubator.apache.org/woden/dev/1.0/milestoneplan.html. > > Specifically, the following items are complete in the M5 Candidate: > Interface extension parsing (DOM). > HTTP binding extensions parsing (DOM). > Unit tests for HTTP binding extensions. > Bug fixes - several JIRAs have been resolved. > Technical documentation has been added to the wiki describing extensions. > > The following items from the M5 plan are incomplete: > Unit tests for Description parsing (DOM) - including Documentation, > Feature, Property > Unit tests for Types parsing (DOM) > Unit test for Interface parsing (DOM) > Unit tests for Binding parsing (DOM) > Unit tests for Interface extension (DOM) > Implement validation logic for SOAP binding extension > Unit tests for validation logic for SOAP binding extension > Update W3C WSDL 2.0 tests in Woden test suite > Review Woden non-functional requirements > > The planned API review is likely to be an ongoing activity as Axis2 and > others start using Woden and providing feedback. There will still be some > specific API review activity in a future milestone plan. The unit tests > still outstanding could not be completed due to the effort required to > implement HTTP binding extensions and improvements to the Woden > implementation, which resulted in significant rework of some validation > test cases. These outstanding unit tests have now been added to the M6 > plan. Note however, that the Woden functionality relating to these > outstanding API tests is already tested to a large extent by the validation > tests, which make use of the Woden API to test WSDL 2.0 assertions. SOAP > extensions validation and validation tests cases could not be completed due > to conflicting project committments, but are rescheduled for M6. > > Other function included in this release, but not listed in the original M5 > plan include: > Support for reading WSDL from different input sources such as a DOM > Element, rather than a URL. > The ValidateWSDL20 Ant task, now packaged in a separate jar, woden-ant.jar. > The stand alone program for converting WSDL 1.1 documents to WSDL 2.0. > > More specific information about M5 can be found in the release notes > located at: > http://people.apache.org/dist/ws/woden/milestones/1.0.0 > M5-incubating/release-notes.html > > > regards, > John Kaputin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
