Author: lmandel
Date: Wed Apr 9 09:45:24 2008
New Revision: 646434
URL: http://svn.apache.org/viewvc?rev=646434&view=rev
Log:
Updated release notes for M8.
Modified:
webservices/woden/trunk/java/release-notes.html
Modified: webservices/woden/trunk/java/release-notes.html
URL:
http://svn.apache.org/viewvc/webservices/woden/trunk/java/release-notes.html?rev=646434&r1=646433&r2=646434&view=diff
==============================================================================
--- webservices/woden/trunk/java/release-notes.html (original)
+++ webservices/woden/trunk/java/release-notes.html Wed Apr 9 09:45:24 2008
@@ -18,22 +18,10 @@
<html>
<head></head>
<body>
-<h1>Woden Incubating 1.0M7 Release Notes</h1>
+<h1>Woden 1.0M8 Release Notes</h1>
-February 2007. This is the Milestone 7 (M7) 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>
-<p>
- The Woden project is an effort undergoing <a
href="http://incubator.apache.org";>incubation at the Apache
- Software Foundation (ASF)</a>, sponsored by the Apache Web Services
PMC. Incubation is
- required of all newly accepted projects until a further review
indicates
- that the infrastructure, communications, and decision making process
have
- stabilized in a manner consistent with other successful ASF projects.
While
- incubation status is not necessarily a reflection of the completeness
or
- stability of the code, it does indicate that the project has yet to be
fully
- endorsed by the ASF.
-</p>
+April 2008. This is the Milestone 8 (M8) release of <a
href="http://ws.apache.org/woden";>Apache Woden</a>.<br />
+The Milestone plan is at <a
href="http://ws.apache.org/woden/dev/1.0/milestoneplan.html";>http://ws.apache.org/woden/dev/1.0/milestoneplan.html</a>.
<h2>Key points</h2>
<p>
@@ -44,38 +32,26 @@
component model and validate their syntax and semantics.
</p>
<p>
- <b>The W3C WSDL 2.0 specification </b>
- is still at W3C Candidate Recommendation (CR) but is close to being ready
to move to
- Proposed Recommendation (PR). There are a few CR issues to be resolved and
some outstanding editorial
- actions for the spec authors, but these should be completed during
February 2007. The move from PR to
- a full W3C Recommendation (equivalent to a formal spec) is now likely
around mid 2007.
+ <b>The WSDL 2.0 specification </b>
+ was published as a W3C Recommendation on June 26, 2007.
</p>
<p>
- <b>The M7 release</b> fully supports the parsing of valid WSDL 2.0
documents
+ <b>The M8 release</b> fully supports the parsing of valid WSDL 2.0
documents
into the WSDL 2.0 Component model, as defined by the WSDL 2.0 spec and
embodied in its
- Test Suite as at the <b>10th February 2007</b>. Within the WSDL 2.0 Test
Suite at that date,
+ Test Suite as at the <b>9th April 2008</b>. Within the WSDL 2.0 Test Suite
at that date,
there were 80 testcases in the Component Model Tests (the 'good' document
testcases)
whose WSDL documents collectively covered all of the WSDL 2.0 elements and
attributes
defined by the spec and those defined for the SOAP and HTTP binding
extensions.
- Woden passed all of these 80 testcases. This 100% compliance level has
been the main
- development objective for the M7 release.
- Any further change to the WSDL 2.0 spec and test suite will be implemented
in Woden
- after the M7 release to maintain this level of compliance.
+ Woden passed all of these 80 testcases.
+ Any further change to the test suite will be implemented in Woden
+ after the M8 release to maintain this level of compliance.
The latest 'Component Model Tests Results' can be seen on the
<a
href="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/Dashboard.html";>
WSDL 2.0 Interop Dashboard</a>.
</p>
<p>
- <b>A second Interop event</b> was held by the WSDL 2.0 Working Group in
November 2006. This
- event consolidated the 'good' WSDL testcases, improved the Dashboard
reporting mechanism and
- helped define Woden's release criteria for M7 (i.e. passing all 'good'
testcases).
- It also initiated a period of more substantial message exchange testing
between the Axis2/Woden
- implementation and the Canon implementation, using both SOAP and HTTP
bindings. As at the release
- of M7, this message exchange testing is progressing well with more varied
and complex scenarios
- being successfully tested. See the 'Message Exchange Test Results' on the
Dashboard for the
- latest progress.
-</p>
-<p>
+ The M8 release includes a new validation framework, which will support
the WSDL 2.0
+ assertions. As of M8 many of the assertions still need to be
implemented.
The main focus of the next release will be to complete Woden's WSDL 2.0
compliance by fully supporting
the assertions defined in the WSDL 2.0 spec. That is, completing Woden's
validation logic to capture
violations of these assertions in the 'bad' WSDL documents in the W3C WSDL
2.0 test suite.
@@ -84,7 +60,6 @@
<ul>
<li>Completing the API to fully support the programmatic creation and
editing of WSDL 2.0 documents.</li>
<li>Modifying the extensions API to improve its usability</li>
- <li>Serializing Woden's WSDL object model to WSDL 2.0 XML documents
(i.e. a WSDLWriter).</li>
<li>Parsing WSDL 1.1 documents into Woden's WSDL 2.0 object model.</li>
</ul>
<p>
@@ -98,54 +73,23 @@
<p>This release includes the following new features:</p>
<ul>
<li>
- Many JIRAs have been resolved during M7 development that dealt with
failures against the W3C WSDL 2.0 test suite.
+ Many JIRAs have been resolved during M8 development. See
+ <a href="http://issues.apache.org/jira/browse/Woden";>Woden's Jira
issue tracker</a> for details.
</li>
<li>
- The readWSDL methods on WSDLReader now return a Description component
instead of DescriptionElement.
- This is because the WSDL information in the WSDL 2.0 Component model
is more useful and easier to
- consume than in the WSDL 2.0 infoset (e.g. flattening document
composition, default values).
- Note that Description.toElement() can still be used if a
DescriptionElement is required.
+ Woden now supports serialization of a WSDL model from the Woden DOM
based model. Work is continuing
+ on serialization for the OM based model.
</li>
<li>
- XMLElement has been introduced to the Woden API to provide a common
representation for 'element' objects
- such as DOM Element and AXIOM OMElement. This eliminates Woden API
dependencies on particular XML parsers
- or object models. As XMLElement wraps most of the behaviour in the
underlying DOM Element or OMElement,
- it has also allowed us to refactor much of the DOMWSDLReader and
OMWSDLReader implementations into a common
- code base.
- </li>
- <li>
- The underlying <xs:schema> and <xs:import> elements
defined directly within <wsdl:types>
- are now accessible via the Woden Schema API as XMLElements. This
allows applications to use additional schema
- processing techniques other than WS-Commons XmlSchema if they so
choose (note, XmlSchema is still used in
- the Woden API to represent schemas).
- </li>
- <li>
- Convenience methods getAllInterfaceFaults and
getAllInterfaceOperations have been added to the Interface
- component API to provide access to faults and operations derived via
interface inheritance.
- </li>
- <li>
- A URL Resolver mechanism has been introduced to resolve URLs via an
optional user-defined catalog.
- This mechanism can greatly improve performance by redirecting remote
requests to locally stored
- documents. It is used internally by Woden for common XML schemas and
DTDs and a default user catalog
- is provided with entries for the W3C WSDL 2.0 testcases, which can be
downloaded and stored locally
- by an ANT script. This mechanism resolves URLs to URLs. Further
development is underway to introduce
- an 'Entity Resolver', which will resolve a URL to the actual XML
content (i.e. an XML catalog).
- </li>
- <li>
- The Feature and Property components have been removed from the WSDL
2.0 spec and so from Woden.
- </li>
- <li>
- The outstanding unit tests for the Element and Component APIs have
been completed.
- </li>
- <li>
- The API Javadoc is more complete.
+ A new validation framework that simplifies the development and
contribution of new assertion checks
+ has been added. This framework will assist in developing tests for the
WSDL 2.0 assertions.
</li>
</ul>
<h2>Current Release Structure</h2>
<p>
- The M7 release is available in 3 types of archives; zip, tar.gz and
tar.bz2.
+ The M8 release is available in 3 types of archives; zip, tar.gz and
tar.bz2.
For each archive type there is a binary and a source distribution archive,
each with
its own MD5 and sha1 checksums.
The source distribution contains the entire Woden Subversion source code
tree.
@@ -153,29 +97,33 @@
The binary distribution contains the Woden API Javadoc and the three
Woden jar files described below:<br />
<ul>
<li>
- woden-api-1.0-incubating-M7.jar - Contains only the
public Woden API (not yet final).
+ woden-api-1.0M8.jar - Contains only the public Woden
API (not yet final).
This jar is suitable for those that wish to create
their own implementation of
the API.
</li>
<li>
- woden-1.0-incubating-M7.jar - Contains the public Woden
API (not yet final) and current DOM
- and AXIOM implementations.
+ woden-impl-dom-1.0M8.jar - Contains the public Woden
API (not yet final) and current DOM
+ implementation.
+ </li>
+ <li>
+ woden-impl-om-1.0M8.jar - Contains the public Woden API
(not yet final) and current Axiom
+ implementation.
</li>
<li>
- woden-ant-1.0-incubating-M7.jar - Contains the Ant task
ValidateWSDL20 used to produce
+ woden-ant-1.0M8.jar - Contains the Ant task
ValidateWSDL20 used to produce
Woden results for the W3C WSDL 2.0 test suite.
</li>
</ul>
Woden depends on the following libraries and these are also included in
the binary distribution:
<ul>
<li>
- Apache WS Commons XmlSchema 1.3.1 (for representing schemas in the
Woden API)
+ Apache WS Commons XmlSchema 1.4.1 (for representing schemas in the
Woden API)
</li>
<li>
Apache Xerces 2.8.1 (used by XmlSchema and by the DOM
implementation of Woden)
</li>
<li>
- Apache WS Commons AXIOM 1.2.3
+ Apache WS Commons AXIOM 1.2.6
</li>
<li>
Apache Commons Logging API 1.1 (used by the AXIOM implementation
of Woden)
@@ -187,10 +135,6 @@
WSDL4J 1.6.2 (used by the standalone WSDL 1.1 conversion
program)
</li>
</ul>
-<p>
-The next release of Woden will produce separate distributions for the DOM and
AXIOM
-implementations, each with only their own dependent libraries.
-</p>
<h2>What's still to do?</h2>
@@ -203,9 +147,6 @@
Various API changes (see JIRA)
</li>
<li>
- Modularizing the build to separate the DOM and AXIOM distributions
- </li>
- <li>
The User Guide on the Woden website requires ongoing improvement.
</li>
<li>
@@ -220,14 +161,11 @@
has not yet been implemented.
</li>
<li>
- Serialization (e.g. WSDLWriter) has not been implemented.
+ Serialization (e.g. WSDLWriter) of the OM model has not been
implemented.
</li>
<li>
Support for non-XML Schema type systems has not yet been
implemented (e.g. RelaxNG, DTDs).
</li>
- <li>
- Entity resolver and an XML catalog mechanism
- </li>
</ul>
<h2>Example Usage</h2>
@@ -274,16 +212,8 @@
report on the Dashboard.
</li>
<li>
- The current extension mechanism mandates 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 will be delivered in
M8 (this was deferred
- on the M7 plan due to lack of time and resources).
- </li>
- <li>
To improve performance, a better mechanism is required for caching
retrieved documents to
- reduce network requests. This will be addressed along side work on
the XML Entity Resolver
- described above.
+ reduce network requests.
</li>
</ol>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
