Author: jkaputin
Date: Thu Jul 19 09:09:15 2007
New Revision: 557668
URL: http://svn.apache.org/viewvc?view=rev&rev=557668
Log:
Update release notes for M7b
Modified:
incubator/woden/branches/M7b/release-notes.html
Modified: incubator/woden/branches/M7b/release-notes.html
URL:
http://svn.apache.org/viewvc/incubator/woden/branches/M7b/release-notes.html?view=diff&rev=557668&r1=557667&r2=557668
==============================================================================
--- incubator/woden/branches/M7b/release-notes.html (original)
+++ incubator/woden/branches/M7b/release-notes.html Thu Jul 19 09:09:15 2007
@@ -18,10 +18,9 @@
<html>
<head></head>
<body>
-<h1>Woden Incubating 1.0M7 Release Notes</h1>
+<h1>Woden Incubating 1.0M7b 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>.
+July 2007. This is the Milestone 7b (M7b) release of <a
href="http://incubator.apache.org/woden";>Apache Woden</a>.<br />
<h2>Incubation Disclaimer</h2>
<p>
@@ -44,39 +43,17 @@
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 W3C WSDL 2.0 specification </b> became a W3C Recommendation on 26
June 2007.
</p>
<p>
- <b>The M7 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,
- 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.
- 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>.
+ <b>The M7b release</b> is an incremental release of M7a which was
released 23 April 2007.
+ It includes some minor corrections to accomodate late changes to the
WSDL 2.0 spec
+ and a few fixes.
+ It is being released ahead of the M8 release to deliver a fix to
Woden's use of
+ WS-Commons XmlSchema in support of the upcoming Axis2 1.3 release.
</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 main focus of the next release will be to complete Woden's WSDL 2.0
compliance by fully supporting
+ The main focus of the next release (M8) 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.
</p>
@@ -98,54 +75,17 @@
<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.
- </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.
- </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.
+ JIRAs WODEN-33, WODEN-149, WODEN-161, WODEN-165, WODEN-168
</li>
<li>
- The API Javadoc is more complete.
+ Fix to DOMWSDLReader to set base URI before calling XmlSchema
</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 M7b 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 +93,29 @@
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.0-incubating-M7b.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
+ woden-1.0-incubating-M7b.jar - Contains the public
Woden API (not yet final) and current DOM
and AXIOM implementations.
</li>
<li>
- woden-ant-1.0-incubating-M7.jar - Contains the Ant task
ValidateWSDL20 used to produce
+ woden-ant-1.0-incubating-M7b.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.3.2 (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.5
</li>
<li>
Apache Commons Logging API 1.1 (used by the AXIOM implementation
of Woden)
@@ -225,9 +165,6 @@
<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>
@@ -278,7 +215,7 @@
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).
+ from 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
