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 lm...@apache.org on 2006/03/07 04:34:23 UTC
svn commit: r383761 - /incubator/woden/java/release-notes.html
Author: lmandel
Date: Mon Mar 6 19:34:23 2006
New Revision: 383761
URL: http://svn.apache.org/viewcvs?rev=383761&view=rev
Log:
Updated release notes for M4.
Modified:
incubator/woden/java/release-notes.html
Modified: incubator/woden/java/release-notes.html
URL: http://svn.apache.org/viewcvs/incubator/woden/java/release-notes.html?rev=383761&r1=383760&r2=383761&view=diff
==============================================================================
--- incubator/woden/java/release-notes.html (original)
+++ incubator/woden/java/release-notes.html Mon Mar 6 19:34:23 2006
@@ -1,9 +1,9 @@
<html>
<head></head>
<body>
-<h1>Woden Incubating 1.0.0 M3 Release Notes</h1>
+<h1>Woden Incubating 1.0.0 M4 Release Notes</h1>
-This is the Third Milestone release of <a href="http://incubator.apache.org/woden">Apache Woden</a>.<br />
+This is the Fourth Milestone 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,7 +20,7 @@
<h2>Key points</h2>
<p>
- This milestone (and up to M4) delivers a DOM-based implementation of Woden.
+ This milestone delivers a DOM-based implementation of Woden.
The main objective is to deliver a full implementation of WSDL 2.0 asap.
A StAX implementation of the Woden API will be the next objective, along
with WSDL 1.1 support and 1.1 to 2.0 conversion.
@@ -36,21 +36,25 @@
<p>This release includes the following new features:</p>
<ul>
<li>
- XML parsing of the WSDL 2.0 service component and its children.
- WSDL import and include are now supported as well, resolving the location URI
- to a WSDL document. However, namespace-only imports (i.e. with no location
- attribute) and the use of an XML Catalog Resolver are deferred to M4.<br />
- <br/>
- (*note: Interface extension via the 'extends' attribute is also deferred until Milestone 4.)
+ SOAP binding extensions were supported in M3 for the WSDL Element model
+ (ext attributes and ext elements), but they are now fully supported in M4 in the
+ WSDL Component model too as component extension properties. New capability
+ has been added to the ExtensionRegistry to handle these component extensions.
+ Related junit testcases have been added to the test suite.
</li>
<li>
- Validation of the binding component and its children.<br />
- (*note: message exchange pattern (MEP) assertions are not included in this milestone.)<br />
- (*note: SOAP and HTTP binding element and component assertions are not included in this milestone .)<br />
+ Validation of the service component and its children.<br />
The specific WSDL 2.0 assertions included in this milestone are:<br />
- Component assertions: Binding-0054, Binding-0055, Binding-0056, Binding-0057, BindingFault-0058,
- BindingFaultReference-0061, BindingFaultReference-0062, BindingMessageReference-0060, BindingOperation-0059
+ Component assertions: Service-0063, Endpoint-0064, Endpoint-0065 and Endpoint-0066.
</li>
+ <li>
+ Namespace-only imports are partially supported for schemas, but support for a
+ URI resolver and XML catalog need to be added to assist with the resolution of
+ imports and includes.
+ </li>
+ <li>
+ A User Guide has been added to the Woden website.
+ </li>
</ul>
<h2>Current Release Structure</h2>
@@ -68,7 +72,7 @@
implementation.
</li>
</ul>
- Woden depends on Apache Xerces 2.7.1 and on Apache Web Service Common XmlSchema.
+ Woden depends on Apache Xerces 2.7.1 and on Apache Web Service Commons XmlSchema 1.0.
These libraries are included in the distribution.
</p>
@@ -79,17 +83,24 @@
you're interested & able!</p>
<ul>
<li>
- As per the revised M4 plan, there is a need for a lot of JUnit tests for the parser.
- These were deferred early on, but are now crucially important for regression testing
- further development - especially as we hope to expand developer participation.
- The unit test backlog with be a major focus for M4.
- </li>
- <li>
- As per the M3 plan, there is a need for user documentation and technical design
- documentation for developers.
- </li>
+ Most of the unit tests on the M4 plan are still outstanding, as the SOAP extensions
+ for the component model took longer than expected. 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.
+ </li>
+ <li>
+ There is a need for technical design documentation for developers.
+ </li>
+ <li>
+ Interface extension via the 'extends' attribute of the WSDL interface element has not
+ been implemented yet.
+ </li>
<li>
- Interface extension via the 'extends' attribute of the WSDL interface element.
+ 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.
</li>
<li>
See also the Task List on the Woden wiki at <a href="http://wiki.apache.org/ws/FrontPage/Woden/TaskList">http://wiki.apache.org/ws/FrontPage/Woden/TaskList</a>.
@@ -126,19 +137,13 @@
We need to think about how to expose these constants on the API.
</li>
<li>
- Xerces and XmlSchema report some schema errors in the W3C test suite. These relate to resolving cross
- references between different schemas (e.g. an inline schema imports the namespace of
- another inline schema and specifies a fragid in its schemaLocation attribute that refers
- to the id attribute of the imported schema).<br/>
- The specific tests that have failed due to these problems are: testChameleon1G, testChameleon2G,
- testChameleon3G, testChameleon4G, testCreditCardFaults1G, testSchemaId1G, and testServiceReference1G1
- </li>
- <li>
- The JUnit test testImportedWSDL1G in the W3C test suite is currently failing because the function
- required for part of the test has not yet been implemented in Woden. This will be addressed in M4.
+ There are currently four JUnit test failures. Failure of test testCreditCardFaults1G is
+ due to a current limitation in Woden with respect to resolving imported schema locations based
+ on the schemaLocation attribute. Failure of tests testService1G, testService2G and testService3G
+ are due to problems with the test cases themselves. These W3C tests are invalid and need to be corrected.
</li>
<li>
- There are insufficient test cases in the test suite for M3. The suite requires more
+ There are insufficient test cases in the test suite for M4. 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org