You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by jk...@apache.org on 2006/09/25 05:34:05 UTC
svn commit: r449556 - in /incubator/woden/trunk/java: build.properties
release-notes.html
Author: jkaputin
Date: Sun Sep 24 20:34:04 2006
New Revision: 449556
URL: http://svn.apache.org/viewvc?view=rev&rev=449556
Log:
Updated build release to M6 and release notes for M6.
Modified:
incubator/woden/trunk/java/build.properties
incubator/woden/trunk/java/release-notes.html
Modified: incubator/woden/trunk/java/build.properties
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/build.properties?view=diff&rev=449556&r1=449555&r2=449556
==============================================================================
--- incubator/woden/trunk/java/build.properties (original)
+++ incubator/woden/trunk/java/build.properties Sun Sep 24 20:34:04 2006
@@ -46,7 +46,7 @@
version = 1.0.0
! The current milestone id
-milestone = 5
+milestone = 6
! The type of build to run. Valid value are R - release, M - milestone, I - integration, N - nightly
buildType = M
Modified: incubator/woden/trunk/java/release-notes.html
URL: http://svn.apache.org/viewvc/incubator/woden/trunk/java/release-notes.html?view=diff&rev=449556&r1=449555&r2=449556
==============================================================================
--- incubator/woden/trunk/java/release-notes.html (original)
+++ incubator/woden/trunk/java/release-notes.html Sun Sep 24 20:34:04 2006
@@ -1,9 +1,9 @@
<html>
<head></head>
<body>
-<h1>Woden Incubating 1.0.0 M5 Release Notes</h1>
+<h1>Woden Incubating 1.0.0 M6 Release Notes</h1>
-This is the Fifth Milestone release of <a href="http://incubator.apache.org/woden">Apache Woden</a>.<br />
+This is the Milestone 6 (M6) release of <a href="http://incubator.apache.org/woden">Apache Woden</a>.<br />
The Milestone plan is at <a href="http://incubator.apache.org/woden/dev/1.0/milestoneplan.html">http://incubator.apache.org/woden/dev/1.0/milestoneplan.html</a>.
<h2>Incubation Disclaimer</h2>
@@ -20,53 +20,54 @@
<h2>Key points</h2>
<p>
- This milestone delivers a DOM-based implementation of Woden.
- The initial objective is to deliver a full implementation of WSDL 2.0 parsing
- and validation. Work is underway to integrate Woden into Axis2.
- A StAX implementation of the Woden API will be the next objective, along
- with WSDL 1.1 support, 1.1 to 2.0 conversion, serialization and full support
- for creating and modifying WSDL documents.
+ Milestone releases will deliver Woden functionality gradually, leading up to a 1.0 release.
+ The objective of a 1.0 release will be to deliver a WSDL processor that fully implements the
+ W3C WSDL 2.0 specification, including parsing WSDL 2.0 documents into the WSDL 2.0 component
+ model and validating their syntax and semantics.
+</p>
+<p>
+Note that the WSDL 2.0 "spec" is currently at W3C Candidate Recommendation and may move to
+Proposed Recommendation towards the end of 2006, then full W3C Recommendation (i.e. a specification)
+sometime in early 2007.
+</p>
+<p>
+ The M6 release delivers an implementation of the Woden API based on DOM and
+ Xerces parsing and an implementation based on AXIOM and StAX parsing.
+</p>
+<p>
+ The DOM implementation of Woden has been integrated into Axis2 and SOAP messaging
+ based on WSDL 2.0 documents was successfully tested by the WSDL 2.0 working group
+ at a W3C Interoperability event in July 2006. Work will commence soon to integrate the
+ AXIOM/StAX implementation of Woden into Axis2.
+</p>
+<p>
+ Some remaining objectives include converting WSDL 1.1 documents into the WSDL 2.0 component
+ model so they can be manipulated via the Woden API, serializing Woden's WSDL object model to
+ WSDL 2.0 documents and full support for programmatically creating and modifying WSDL 2.0 documents.
</p>
<p>
The Woden framework and programming model are similar to WSDL4J, such as the
- factory, reader and WSDL xml object model. Other features will be reused too,
+ factory, reader and WSDL xml object model. Other features have been reused or adapted too,
such as the extension mechanism.
</p>
-<h2>What's in this release?</h2>
+<h2>What's new in this release?</h2>
<p>This release includes the following new features:</p>
<ul>
<li>
- Parsing of HTTP binding and endpoint extensions are now fully supported by Woden,
- as HTTP extension elements and attributes via the Element API and
- as HTTP component extension properties via the Component API.
- Related junit testcases have been added to the test suite.
+ An implementation of the Woden API based on StAX parsing and AXIOM. This implementation uses the
+ same programming model (API) as the DOM implementation, however a different WSDLFactory implementation
+ class is needed to instantiate the StAX/AXIOM implementation (i.e. OMWSDLFactory).
</li>
<li>
- Interface extension is now fully supported, so for example Interface and Binding nested
- components can now refer to derived or inherited faults and operations.
+ The way that elements are created and added by the Woden API has been change to better
+ support the scoping described by the WSDL 2.0 specification. The createXXXElement factory
+ methods on <code>DescriptionElement</code> have been removed and instead the addXXXElement
+ methods present on all parent elements instantiate and add the appropriate child elements.
+ The relevant child elements have been changed to store their name as an NCName rather than
+ a QName, but the QName is still available via the API (i.e. derived from the target namespace).
</li>
- <li>
- The WSDLReader API has been expanded to support reading WSDL from sources other
- than a URI - for example, from a DOM Element or from an InputSource.
- </li>
- <li>
- A technical description of the extension mechanism and the SOAP and HTTP extension
- implementations has been added to the Woden Wiki.
- </li>
- <li>
- An Ant task for using Woden from Ant to perform WSDL 2.0 validation. The task is called
- ValidateWSDL20 and is packaged in a new jar file, woden-ant.jar. To use Woden with Ant add the
- jar files woden.jar and woden-ant.jar to your Ant installation. The User Guide on the Woden
- website will be updated soon with details of this Ant task.
- </li>
- <li>
- A standalone converter program that uses WSDL4J to read a WSDL 1.1 service definition then
- serializes it as a WSDL 2.0 description. org.apache.woden.tool.converter.Convert is packaged in
- the woden.jar file. Investigation is underway to incorporate this conversion logic into Woden's
- planned support for WSDL 1.1 to 2.0 conversion.
- </li>
</ul>
<h2>Current Release Structure</h2>
@@ -81,15 +82,33 @@
</li>
<li>
woden.jar - Contains the public Woden API (not yet final) and current DOM
- implementation.
+ and AXIOM implementations.
</li>
<li>
woden-ant.jar - Contains the Ant task ValidateWSDL20.
</li>
</ul>
- Woden depends on Apache Xerces 2.8.0 and on Apache Web Service Commons XmlSchema 1.0.
- These libraries are included in the distribution. The standalone WSDL 1.1 conversion
- program depends on WSDL4J 1.52 and this library is also included in the distribution.
+ Woden depends on the following libraries and these are included in the distribution:
+ <ul>
+ <li>
+ Apache WS Commons XmlSchema 1.1 (for representing schemas in the Woden API)
+ </li>
+ <li>
+ Apache Xerces 2.8.0 (used by XmlSchema and by the DOM implementation of Woden)
+ </li>
+ <li>
+ Apache WS Commons AXIOM 1.1
+ </li>
+ <li>
+ Apache Commons Logging API 1.1 (used by the AXIOM implementation of Woden)
+ </li>
+ <li>
+ StAX 1.0.1 API and the Woodstox 2.9.3 implementation (used by the AXIOM implementation of Woden)
+ </li>
+ <li>
+ WSDL4J 1.52 (used by the standalone WSDL 1.1 conversion program)
+ </li>
+ </ul>
</p>
@@ -99,18 +118,16 @@
you're interested & able!</p>
<ul>
<li>
- A URL resolver mechanism needs to be implemented, something like an EntityResolver or CatalogResolver.
+ Work is well underway on a URL resolver mechanism.
</li>
<li>
- Unit tests the extensions are mostly complete, but tests for the core WSDL 2.0
+ Unit tests for the WSDL extensions are mostly complete, but tests for the core WSDL 2.0
Component model and its underlying Element model are still largely outstanding.
- These were a major plan item for M5 but were overshadowed by the effort required
- to complete the HTTP extensions and test cases. These are still crucially important
- for regression testing further development and will remain a major focus item for the
- next milestone.
+ These are still crucially important for regression testing further development and
+ will remain a major focus item for the next milestone.
</li>
<li>
- The User Guide added after M3 needs updating to reflect the functional additions for M4 and M5.
+ The User Guide added after M3 needs updating to reflect the functional additions up to M6.
</li>
<li>
Technical design documentation for developers needs to be created, probably on the Woden Wiki.
@@ -120,8 +137,8 @@
a Woden WSDL 2.0 object model from a parsed WSDL 1.1. document.
</li>
<li>
- Validation of MEPs and extension elements (such as those for SOAP and HTTP bindings and
- for type systems other than XML schema) has not yet been implemented.
+ Validation of MEPs and extension elements (such as those for SOAP and HTTP bindings)
+ has not yet been implemented.
</li>
<li>
Serialization (e.g. WSDLWriter) has not been implemented.
@@ -166,24 +183,38 @@
<ol>
<li>
+ The "testSchemaId1G" testcase from the W3C WSDL 2.0 test suite is failing since the
+ change to XmlSchema 1.1. This appears to be due to a fragid specified for the
+ schemaLocation in a schema import. It requires investigation and resolving, possibly
+ in XmlSchema rather than Woden.
+ </li>
+ <li>
+ The StAX/AXIOM implementation is less complete than the Xerces/DOM implementation.
+ For example, extensions are not yet supported as this is awaiting the removal of
+ some DOM dependencies from the Woden API. This work is underway and will be completed
+ for Milestone 7.
+ </li>
+ <li>
Currently, the only type system supported is W3C XML Schema and this is exposed at
certain points of the API (through the use of the XmlSchema interface). Later on we
will consider more general, extendable support for other type systems.
</li>
<li>
- In the Element API, certain 'name' attributes are being handled as QNames whereas they
- are defined in the infoset as NCNames. This is being fixed.
- </li>
- <li>
- There are various failures in the test results for the Component Interchange format testing
- being conducted by the WSDL 2.0 Working Group. These need to be investigated prior to the
- W3C WSDL 2.0 Interop event in early July 2006.
+ There are still failures in the W3C test suite results for the Component Interchange format testing
+ being conducted by the WSDL 2.0 Working Group. Some of these were resolved at the
+ W3C WSDL 2.0 Interop event in early July 2006, but the remainder require investigation.
</li>
<li>
- There are insufficient test cases in the test suite for M5. The suite requires more
+ There are insufficient test cases in the test suite for M6. The suite requires more
junit tests for the Woden framework and the W3C WSDL test suite is in the process of
- being annotated with assertions that tie each test to a specific part of the WSDL 2.0
- spec.
+ being annotated with assertions that tie each testcase to a validation
+ rule specified in the WSDL 2.0 spec.
+ </li>
+ <li>
+ The current extension mechanism requires statically typed interfaces for each type of
+ extension. This requires the client application to know each required extension and
+ its API. Some investigation has been done on a more flexible, dynamic extension
+ mechanism and any changes that arise from this should be delivered in M7.
</li>
</ol>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org