Author: jkaputin
Date: Wed Jun 7 21:11:42 2006
New Revision: 412644
URL: http://svn.apache.org/viewvc?rev=412644&view=rev
Log:
Updated the release notes for M5.
Modified:
incubator/woden/java/release-notes.html
Modified: incubator/woden/java/release-notes.html
URL:
http://svn.apache.org/viewvc/incubator/woden/java/release-notes.html?rev=412644&r1=412643&r2=412644&view=diff
==============================================================================
--- incubator/woden/java/release-notes.html (original)
+++ incubator/woden/java/release-notes.html Wed Jun 7 21:11:42 2006
@@ -1,9 +1,9 @@
<html>
<head></head>
<body>
-<h1>Woden Incubating 1.0.0 M4 Release Notes</h1>
+<h1>Woden Incubating 1.0.0 M5 Release Notes</h1>
-This is the Fourth Milestone release of <a
href="http://incubator.apache.org/woden";>Apache Woden</a>.<br />
+This is the Fifth 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>
@@ -21,9 +21,11 @@
<h2>Key points</h2>
<p>
This milestone delivers a DOM-based implementation of Woden.
- The main objective is to deliver a full implementation of WSDL 2.0
asap.
+ 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 and 1.1 to 2.0 conversion.
+ with WSDL 1.1 support, 1.1 to 2.0 conversion, serialization and full
support
+ for creating and modifying WSDL documents.
</p>
<p>
The Woden framework and programming model are similar to WSDL4J, such
as the
@@ -36,24 +38,22 @@
<p>This release includes the following new features:</p>
<ul>
<li>
- 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.
+ 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.
</li>
<li>
- Validation of the service component and its children.<br />
- The specific WSDL 2.0 assertions included in this milestone are:<br />
- Component assertions: Service-0063, Endpoint-0064, Endpoint-0065 and
Endpoint-0066.
+ Interface extension is now fully supported, so for example Interface
and Binding nested
+ components can now refer to derived or inherited faults and operations.
</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.
+ 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 User Guide has been added to the Woden website.
+ A technical description of the extension mechanism and the SOAP and
HTTP extension
+ implementations has been added to the Woden Wiki.
</li>
</ul>
@@ -83,32 +83,39 @@
you're interested & able!</p>
<ul>
<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
+ A URL resolver mechanism needs to be implemented, something
like an EntityResolver or CatalogResolver.
+ </li>
+ <li>
+ Unit tests the 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.
</li>
<li>
- The User Guide added after M3 needs updating to reflect the
functional additions for M4.
+ The User Guide added after M3 needs updating to reflect the
functional additions for M4 and M5.
</li>
<li>
- There is a need for technical design documentation for
developers.
+ Technical design documentation for developers needs to be
created, probably on the Woden Wiki.
</li>
<li>
- Interface extension via the 'extends' attribute of the WSDL
interface element has not
- been implemented yet.
+ Integrating the stand-alone WSDL 1.1 to 2.0 converter tool into
Woden to produce
+ 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.
</li>
<li>
- HTTP extension elements have not yet been implemented.
+ Serialization (e.g. WSDLWriter) has not been implemented.
</li>
<li>
Support for non-XML Schema type systems has not yet been
implemented.
</li>
-
+ <li>
+ See the Woden JIRA issues at <a
href="http://issues.apache.org/jira/browse/Woden";>http://issues.apache.org/jira/browse/Woden</a>.
+ </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>.
</li>
@@ -116,17 +123,28 @@
<h2>Example Usage</h2>
-<p>
- WSDLFactory factory = WSDLFactory.newInstance();<br />
- WSDLReader reader = factory.newWSDLReader();<br />
- reader.setFeature(ReaderFeatures.VALIDATION_FEATURE_ID, true); <--
enable WSDL 2.0 validation (optional)<br />
- DescriptionElement desc = reader.readWSDL(wsdlLoc); <-- the
<description> element<br />
- Description descComp = desc.toComponent(); <-- the
Description component<br />
-</p>
-<p>
- A custom error handler can also be specified as follows:<br />
- DescriptionElement desc = reader.readWSDL(wsdlLoc, handler);
-</p>
+<pre>
+ WSDLFactory factory = WSDLFactory.newInstance();
+ WSDLReader reader = factory.newWSDLReader();
+ reader.setFeature(ReaderFeatures.VALIDATION_FEATURE_ID, true); <--
enable WSDL 2.0 validation (optional)
+ DescriptionElement desc = reader.readWSDL(wsdlLoc); <-- the
<description> element
+ Description descComp = desc.toComponent(); <-- the
Description component
+</pre>
+ A custom error handler can also be specified as follows:<br />
+<pre>
+ DescriptionElement desc = reader.readWSDL(wsdlLoc, handler);
+</pre>
+ WSDL can be now be parsed from a DOM Element, DOM Document or InputSource
using a WSDLSource object:<br />
+<pre>
+ WSDLFactory factory = WSDLFactory.newInstance();
+ WSDLReader reader = factory.newWSDLReader();
+ reader.setFeature(WSDLReader.FEATURE_VALIDATION, true);
+ WSDLSource wsdlSource = reader.createWSDLSource();
+ wsdlSource.setBaseURI(wsdlURI);
+ wsdlSource.setSource(docEl);
+ DescriptionElement desc = reader.readWSDL(wsdlSource);
+ Description descComp = desc.toComponent();
+</pre>
<h2>Known Problems/Issues</h2>
@@ -137,19 +155,16 @@
will consider more general, extendable support for other type
systems.
</li>
<li>
- Constants that represent possible type systems (e.g. W3 XML
Schema) and type system APIs
- (e.g. XML Schema API) are defined in
org.apache.woden.internal.wsdl20.Constants. This is
- part of the implementation, not part of the API. Users of the
API may need access to these
- constants to query type system support via TypesElement,
ElementDeclaration or TypeDefinition.
- We need to think about how to expose these constants on the API.
+ 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 is currently one JUnit test failure. Failure of test
testCreditCardFaults1G is
- due to a current limitation in Woden with respect to resolving
imported schema locations based
- on the schemaLocation attribute.
+ 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.
</li>
<li>
- There are insufficient test cases in the test suite for M4. The
suite requires more
+ There are insufficient test cases in the test suite for M5. 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
