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 2005/12/07 01:30:15 UTC
svn commit: r354634 - /incubator/woden/java/release-notes.html
Author: lmandel
Date: Tue Dec 6 16:30:12 2005
New Revision: 354634
URL: http://svn.apache.org/viewcvs?rev=354634&view=rev
Log:
Updated release notes.
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=354634&r1=354633&r2=354634&view=diff
==============================================================================
--- incubator/woden/java/release-notes.html (original)
+++ incubator/woden/java/release-notes.html Tue Dec 6 16:30:12 2005
@@ -1,9 +1,9 @@
<html>
<head></head>
<body>
-<h1>Woden 1.0.0 M1 Release Notes</h1>
+<h1>Woden Incubating 1.0.0 M2 Release Notes</h1>
-This is the First Milestone release of Apache Woden.
+This is the Second Milestone release of Apache Woden.
<h2>Key points</h2>
<p>
@@ -13,9 +13,9 @@
with WSDL 1.1 support and 1.1 to 2.0 conversion.
</p>
<p>
- Woden uses the W3C XML Schema API implemented in Xerces for handling
- XML schema content, although the intention is to switch to the XmlSchema
- model in Apache ws-commons at a later point.
+ In M2 the XML Schema model has been changed from the W3C XML Schema API
+ implemented in Xerces for handling to switch to the XmlSchema
+ model in Apache ws-commons.
</p>
<p>
The Woden framework and programming model are similar to WSDL4J, such as the
@@ -25,21 +25,29 @@
<h2>What's in this release?</h2>
-<p>This release includes the following features:</p>
+<p>This release includes the following new features:</p>
<ul>
<li>
- XML parsing of description, types, xs:import, xs:schema, interface, fault,
- documentation, property, feature.<br />
+ XML parsing of WSDL 2.0 interface and binding components and their children.
+ (The children include components such as interface operations, and interface faults.)<br />
<br/>
- (*note: this does not include interface <operation> and its child elements
- - input, output, etc., or the <constraint> element within the property element.)
+ (*note: WSDL import and include elements are not supported in this milestone.)
</li>
<li>
- Creation of a Component model, with types components but no interface components yet.
- The component model currently includes Description, ElementDeclaration, TypeDefinition.
+ Creation of a Component model with Description, ElementDeclaration, TypeDefinition,
+ interface, and binding components.
</li>
<li>
- Validation feature support and XML Schema based validation.
+ Validation feature support, XML Schema based validation, and validation the types and
+ interface elements and their children as well as the interface component and its children.<br />
+ (*note: message exchange pattern (MEP) assertions are not included in this milestone.)<br />
+ The specific WSDL 2.0 assertions included in this milestone are:<br />
+ Document assertions: Description-0025, Interface-0031, Schema-0016, Schema-0017, Schema-0018,
+ Schema-0019, Schema-0020, Schema-0052<br />
+ Component assertions: FeatureRef-0046, FeatureRef-0047, Interface-0027, Interface-0030,
+ InterfaceFault-0028, InterfaceFault-0032, InterfaceFaultReference-0045, InterfaceMessageReference-0041,
+ InterfaceMessageReference-0042, InterfaceOperation-0029, InterfaceOperation-0035, MEP-0037,
+ Property-0049, Property-0050, PropertyRef-0048
</li>
</ul>
@@ -58,7 +66,7 @@
implementation.
</li>
</ul>
- Woden depends on Apache Xerces 2.7.1 and has plans to depend on Apache Web Service Common XmlSchema.
+ Woden depends on Apache Xerces 2.7.1 and on Apache Web Service Common XmlSchema.
These libraries are included in the distribution.
</p>
@@ -68,14 +76,11 @@
<p>Please see a list of what we think needs doing - and please consider helping out if
you're interested & able!</p>
<ul>
- <li>
- From M1 plan, finish the parsing of interface <operation> element and creation
- of the InterfaceOperation, InterfaceMessageReference, InterfaceFaultReference
- Feature and Property components in the Component model.
- </li>
<li>
- As per the M2 plan, parse elements and create Component model for the binding information,
- Create validation framework and validator logic for types and interface components.
+ As per the M2 plan, there is a need for a lot of JUnit tests for the parser.
+ </li>
+ <li>
+ As per the M2 plan, there is a need for user documentation.
</li>
</ul>
@@ -84,20 +89,15 @@
<p>
WSDLFactory factory = WSDLFactory.newInstance();<br />
WSDLReader reader = factory.newWSDLReader();<br />
- DescriptionElement desc = reader.readWSDL(wsdlLoc); <-- the <description> element<br />
- Description descComp = desc.getDescriptionComponent(); <-- the Description component<br />
+ reader.setFeature(ReaderFeatures.VALIDATION_FEATURE_ID, true); <-- enable WSDL 2.0 validation (optional)
+ DescriptionElement desc = reader.readWSDL(wsdlLoc); <-- the <description> element<br />
+ Description descComp = desc.getDescriptionComponent(); <-- the Description component<br />
</p>
<h2>Known Problems/Issues</h2>
<ol>
<li>
- Some validation and error reporting has been included in the parsing logic in WSDLReader
- for errors such as REQUIRED attributes missing (e.g. target NS on <description>). As the
- validation logic is developed for milestone 2 this may well change. For example, we
- may parse the entire wsdl ignoring the errors, then let the validator handle it.
- </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 XSModel interface). Later on we
will consider more general, extendable support for other type systems.
@@ -110,24 +110,17 @@
We need to think about how to expose these constants on the API.
</li>
<li>
- Support for extension elements and attributes within the interface elements has not yet
- been implemented, but will be considered for M2 along with the extensibility required for
- bindings.
- </li>
- <li>
- Xerces reports some schema errors in the W3C test suite. These relate to resolving cross
+ 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). Possible solutions or work arounds to these
- problems emerged close to the M1 date, but we didn't have time to resolve them. They should
- be corrected for M2.
+ problems emerged close to the M2 date, but we didn't have time to resolve them.<br/>
</li>
<li>
- There are in sufficient test cases in the test suite for M1. The suite requires more
- junit tests for the Woden framework and the W3C wsdl test suite is in the process of
+ There are insufficient test cases in the test suite for M2. 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. Our earliest priority for the M2 timeframe will be improving the test suite for
- the M1 function.
+ spec.
</li>
</ol>
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org