svn commit: r505234 - /incubator/woden/branches/M7/release-notes.html

[jk...@apache.org]

Author: jkaputin
Date: Fri Feb  9 01:55:15 2007
New Revision: 505234

URL: http://svn.apache.org/viewvc?view=rev&rev=505234
Log:
Updated the Release Notes for M7.

Modified:
    incubator/woden/branches/M7/release-notes.html

Modified: incubator/woden/branches/M7/release-notes.html
URL: http://svn.apache.org/viewvc/incubator/woden/branches/M7/release-notes.html?view=diff&rev=505234&r1=505233&r2=505234
==============================================================================
--- incubator/woden/branches/M7/release-notes.html (original)
+++ incubator/woden/branches/M7/release-notes.html Fri Feb  9 01:55:15 2007
@@ -64,7 +64,7 @@
 <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 
-    established Woden's compliance criteria for the M7 release.
+    established Woden's compliance criteria for the M7 release (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 
@@ -80,7 +80,7 @@
 	<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>Reading WSDL 1.1 documents and converting them into Woden's WSDL 2.0 object model.</li>
+	<li>Parsing WSDL 1.1 documents into Woden's WSDL 2.0 object model.</li>
 	</ul>
 <p>
 	The Woden parser framework and its programming model originated from WSDL4J, a WSDL 1.1 processor.
@@ -238,14 +238,14 @@
 <pre>
    Description descComp = reader.readWSDL(wsdlLoc, myErrorHandler);
 </pre>
-   WSDL can be now be parsed from a DOM Element, DOM Document or InputSource using a WSDLSource object:<br />
+   WSDL can be parsed from some underlying object or byte stream content (rather than a URL) using a WSDLSource object:<br />
 <pre>
    WSDLFactory factory = WSDLFactory.newInstance();
    WSDLReader reader = factory.newWSDLReader();
    reader.setFeature(WSDLReader.FEATURE_VALIDATION, true);
    WSDLSource wsdlSource = reader.createWSDLSource();  //the WSDLSource impl is specific to the WSDLReader impl
    wsdlSource.setBaseURI(wsdlURI);
-   wsdlSource.setSource(docEl);
+   wsdlSource.setSource(wsdlSrc);                      //where wsdlSrc might be a DOM Document or Element object
    Description descComp = reader.readWSDL(wsdlSource);
 </pre>
 
@@ -263,15 +263,22 @@
    	</li>
 	<li>
 	    Validation does not yet cover all WSDL 2.0 assertions and in fact, the W3C WSDL 2.0 
-	    Assertion Test Suite Coverage reports shows these 'bad' WSDL testcases are not yet 
-	    complete.  So, there will currently be some Woden failures on the WSDL 2.0 Validation Tests 
+	    Assertion Test Suite Coverage report shows that 'bad' WSDL testcases for some of these 
+	    assertions do not not yet exist (i.e. this test suite is incomplete).
+	    So, there will currently be some Woden failures on the WSDL 2.0 Validation Tests 
 	    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.
+	    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.  
 	</li>
 </ol>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org