Woden 1.0 Milestone plan

Development of Woden will proceed according to the following milestone plan.

All dates should be taken as approximate and subject to change.

• WSDL 2.0 types parsing (DOM)
• Unit tests for types parsing (DOM)
• WSDL 2.0 Interface parsing (DOM)
• Unit tests for Interface parsing (DOM)
• Create validation framework including extension mechanism
• Unit tests for validation framework
• Create Ant script for build process
• Update website to follow new Apache Web services website layout
• Update technical documentation about Woden design and implementation on Wiki
• Create initial user documentation

• WSDL 2.0 Interface parsing (DOM)
• Unit tests for Interface parsing (DOM)
• Create validation framework
• Create validation framework extension mechanism
• WSDL 2.0 Binding parsing (DOM)
• WSDL 2.0 Binding extensibility mechanism (DOM)
• Unit tests for Binding parsing (DOM)
• WSDL 2.0 SOAP Binding extension (DOM)
• Unit tests for 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
• Update technical documentation about Woden design and implementation on Wiki
• Create initial user documentation

• Parsing of WSDL 2.0 import and include (DOM)
• Unit tests for import and include parsing (DOM)
• WSDL 2.0 HTTP Binding extension (DOM)
• Unit tests for HTTP Binding extension (DOM)
• WSDL 2.0 Service parsing (DOM)
• Unit tests for Service parsing (DOM)
• Implement validation logic for Binding
• Unit tests for validation logic for Binding
• Integrate W3C WSDL 2.0 Binding tests into Woden test suite
• Investigate WSDL 2.0 parsing with StAX
• Update technical documentation about Woden design and implementation on Wiki
• Create initial user documentation

• 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)
• Parsing of WSDL 2.0 interface extension (DOM)
• Unit tests for interface extension parsing (DOM)
• Unit tests for SOAP binding extensions parsing (DOM)
• WSDL 2.0 HTTP Binding extension (DOM)
• Unit tests for HTTP Binding extension (DOM)
• Implement validation logic for Service
• Unit tests for validation logic for Service
• Integrate W3C WSDL 2.0 Service tests into Woden test suite
• API review
• Review Woden non-functional requirements
• Bug fixes
• Update technical documentation about Woden design and implementation on Wiki
• Create initial user documentation

• 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)
• Parsing of WSDL 2.0 interface extension (DOM)
• Unit tests for interface extension parsing (DOM)
• WSDL 2.0 HTTP Binding extension (DOM)
• Unit tests for HTTP Binding 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
• API review
• Review Woden non-functional requirements
• Bug fixes
• Update technical documentation about Woden design and implementation on Wiki

• Implement Woden API using StAX and AXIOM
• Change API to enforce correct scoping of nested elements

Updated Feb 6th: Finishing off some API Javadoc. Expect to start the release vote today or tomorrow.

Updated Jan 26th: The M7 release date has been delayed from Jan 29th by 1 week and two of the release defining JIRAs have been deferred until the release following M7 (WODEN-47 and WODEN-56).

The release-defining criteria for M7 are:

• to pass all of the 'good' document test cases in the W3C WSDL 2.0 suite, as this will help the W3C WSDL 2.0 spec progress from CR to PR.
• to implement any required API changes sooner rather than later to stablize the API
• to implement unit tests outstanding from previous milestone plans
• to fix major bugs

While complete WSDL validation (i.e. support for all assertions in the WSDL 2.0 spec and the Validation test cases in the WSDL 2.0 Test Suite) is a major objective of the Woden project, it is not a mandatory criteria for the M7 release. However, it is high priority post-M7.

See the Woden JIRAs marked with Version M7 for a list of outstanding function planned for M7. Of those, the release-defining JIRAs for M7 (those that are "must-do") are:

• 'good' test case failures:
  • WODEN-10 SchemaId-1G
  • WODEN-86 MessageTest-1G
  • WODEN-98 LocationTemplate-1G
  • WODEN-99 MessageTest-2G
  • WODEN-100 Schema-1G
  • WODEN-101 SparqlQuery-1G
  • WODEN-102 SparqlQuerySimplified-1G
• API changes:
  • WODEN-47 generic collections of extensions as well as/instead of static typing
  • WODEN-56 remove need to use *internal* classes when coding extensions
  • WODEN-87 methods in Interface API to 'flatten' interface inheritance
  • WODEN-119 readWSDL args should be URI instead of String (CANCELLED)
  • WODEN-120 readWSDL methods should return Description not DescriptionElement
  • WODEN-126 provide the underlying schema element
  • WODEN-129 add query parameter separator to SOAP/HTTP extensions
• Outstanding unit tests:
  • WODEN-49 tests for ImportElement and IncludeElement
  • WODEN-50 tests for Service and Endpoint
  • WODEN-51 tests for Description and DescriptionElement
  • WODEN-53 tests for TypesElement, ElementDeclaration, TypeDefinition
  • WODEN-54 tests for Interface and InterfaceElement and their children
  • WODEN-55 tests for Binding and BindingElement and their children
• Others:
  • WODEN-45 changes to "ASF Source Header and Copyright Notice Policy"
  • WODEN-85 Common, standard schema and DTD files
  • WODEN-118 NPE when import location does not resolve to a document
  • WODEN-123 Include ALL schema elements and types in Component model

The M7a release is an incremental release of M7 which delivers an essential fix. Namely, the change of the WSDL 2.0 namespaces from the CR format "http://www.w3.org/2006/01/wsdl*" to the shortened format "http://www.w3.org/ns/wsdl*". The W3C WSDL 2.0 test suite has been updated to use this new namespace format and as with the M7 release, M7a is still 100% compliant with the Component Model test suite (ie. the 'good' WSDL documents).

The new features included in this release are described in these Woden JIRAs:

• WODEN-153, Use new WSDL 2.0 Namespaces
• WODEN-154, URI Resolver error "URI is not hierarchical"

The M7b release is a further incremental release of M7 which includes some minor corrections to accomodate late changes to the WSDL 2.0 spec and a number of fixes, including Woden's use of WS-Commons XmlSchema.

The new features included in this release are described in these Woden JIRAs:

• WODEN-33, DocumentationElement should extend NestedElement
• WODEN-149, Update Woden with New WSDL 2.0 Assertions Numbers for Proposed Recommendation
• WODEN-161, Style default from interface not applied to operations
• WODEN-165, SAX attribution in NOTICE file is not required
• WODEN-168, OMXMLElementTest class incorrectly returning the DOMXMLElementTest class as its test suit

Also included is a fix to DOMWSDLReader to set base URI before calling XmlSchema.

The M8 release will complete Woden's compliance with the W3C WSDL 2.0 Recommendation. The M7 release completed spec-compliance for valid WSDL documents. M8 will complete spec-compliance for invalid WSDL by supporting all of the validation assertions defined by the Recommendation.

The release-defining criteria for M8 are:

• to continue to pass all of the 'good' WSDL test cases in the W3C WSDL 2.0 test suite
• to validate all of the expected assertion failures from the 'bad' WSDL test cases in the W3C WSDL 2.0 test suite
• to implement the changes to the extension architecture deferred from M7
• to support user-defined WSDL extensions AND user-defined validation of those extensions

See the Woden JIRAs to be fixed for Version M8 for the remaining function planned for M8.

The JIRAs considered part of the release-defining criteria are:

• WODEN-39 W3C WSDL2 tests should include assertions
• WODEN-47 Extensions as generic collections
• WODEN-56 Extensions API should not use *internal* classes
• WODEN-62 Adding an assertion check should be simple
• WODEN-74 Missing QName resolution error for {interface fault} property of Interface
• WODEN-103 Several binding assertion failures
• WODEN-104 Several import/include assertion failures
• WODEN-105 Several interface assertion failures
• WODEN-106 Several types/schema assertions failures
• WODEN-107 Several qname assertion failures
• WODEN-122 Implement EBNF grammar for {http location}
• WODEN-156 User extensions for Interface
• WODEN-157 SOAP binding reuse of HTTP properties
• WODEN-158 SOAPBindingOperationExtensions does not have isHttpLocationIgnoreUncited
• WODEN-181 Add method BindingMessageReferenceElement.getInterfaceMessageReferenceElement()

The 1.0 release of Woden will support DOM parsing and validation of WSDL 2.0 documents. The main objective of this release will be to deliver a stable Woden API. That is, a committed API for future releases. User feedback from the milestone releases so far has resulted in ongoing improvements to the Woden API. Further work will be required for the 1.0 release to agree the final API. Some API review issues have already been caputured on the Woden wiki.