Release Notes - Woden - Version M8 - HTML format

Bug

• [WODEN-33] - DocumentationElement should extend NestedElement
• [WODEN-74] - Validation does not report a QName resolution error for the {interface fault} property of InterfaceFaultReference
• [WODEN-115] - Support WSDL 2.0 <description> nested within other XML documents
• [WODEN-135] - Change lookup strategy for interface and binding fault reference elements to check extended interfaces
• [WODEN-136] - Message content model should not be represented in the Element API
• [WODEN-137] - QNameTest.testGoodDeserializeQNameWithoutPrefix fails for Sun 1.5.0_07->_11 JREs
• [WODEN-141] - DescriptionElement.getTypesElement() should not be a factory method
• [WODEN-148] - HTTPLocation not parsed correctly
• [WODEN-150] - schema.catalog fails to be correctly located
• [WODEN-151] - wsdl4j license not included
• [WODEN-155] - HTTPLocation must support the EBNF grammar for parsing whttp:location
• [WODEN-159] - InterfaceImpl.getAllInterfaceOperations and getAllInterfaceFaults are not quite recursive
• [WODEN-160] - Woden doesn't specify the default MEP to use if none is specified
• [WODEN-162] - parser does not handle faults with element="#any" etc.
• [WODEN-165] - SAX attribution in NOTICE file is not required
• [WODEN-166] - Use svn:eol-style=native
• [WODEN-167] - OMWSDLReader mismatch with DOMWSDLFactory
• [WODEN-168] - OMXMLElementTest class incorrectly returning the DOMXMLElementTest class as its test suit.
• [WODEN-172] - FlickrHTTP-1G test fails due to NS prefix and interface extension errors
• [WODEN-173] - Correct the WSDL object model implementation inheritance
• [WODEN-174] - Include the prefix in QNames from the target namespace
• [WODEN-175] - ImportElement and IncludeElement should extend NestedElement
• [WODEN-176] - Remove the setParentElement method from the API
• [WODEN-189] - NPE when interface extension used with Element API
• [WODEN-191] - URISyntaxException in SimpleURIResolver when path contains spaces
• [WODEN-192] - schemaLocation URI not resolved correctly using jar files
• [WODEN-193] - Problem parsing a WSDL having XML as the documentation
• [WODEN-199] - Remove return type from validate method
• [WODEN-201] - Woden throws an error when the targetNamespace of the WSDL is urn:wsdlSamples
• [WODEN-203] - WSDL 2.0 codegeration fails in Axis2 due to Woden assertion

Improvement

• [WODEN-3] - Add the component name to the Schema-1066 assertion method
• [WODEN-32] - implement toString() methods to aid usability in debuggers
• [WODEN-67] - Modularize the build to separate API and implementations
• [WODEN-140] - DescriptionElement.getNamespaces() should have a type-safe return type
• [WODEN-142] - <documentation> element should not be wrapped as java.lang.Object
• [WODEN-163] - Provide a mechanism for registering extensions and their error message formats independently of the API.
• [WODEN-171] - Remove QNameUtils class
• [WODEN-177] - Share client-configurable objects across the Woden implementation
• [WODEN-178] - DescriptionImpl methods addElementDeclaration and addTypeDefinition should not be public
• [WODEN-179] - Remove WSDLReader.readWSDL methods that take an ErrorHandler parameter
• [WODEN-181] - getInterfaceMessageReferenceElement() method required on BindingMessageReferenceElement
• [WODEN-195] - Improve formatting of messages with no message parameters
• [WODEN-198] - Create Interface1009 Assertion Class
• [WODEN-200] - Create Interface1010 Assertion Class

New Feature

• [WODEN-184] - WSDL-viewer contribution

Task

• [WODEN-149] - Update Woden with New WSDL 2.0 Assertions Numbers for Proposed Recommendation

Test

• [WODEN-70] - Running Woden test suite in network isolation mode
• [WODEN-187] - Create a Test Suite for the WSDL Viewer

The text area below allows the project release notes to be edited and copied to another document.