Author: jkaputin
Date: Tue Nov 20 07:05:38 2007
New Revision: 596710
URL: http://svn.apache.org/viewvc?rev=596710&view=rev
Log:
Update the M8 milestone plan and the comments for
the 1.0 release.
Modified:
incubator/woden/Site/build/site/dev/1.0/milestoneplan.html
incubator/woden/Site/src/documentation/content/xdocs/dev/1.0/milestoneplan.xml
Modified: incubator/woden/Site/build/site/dev/1.0/milestoneplan.html
URL:
http://svn.apache.org/viewvc/incubator/woden/Site/build/site/dev/1.0/milestoneplan.html?rev=596710&r1=596709&r2=596710&view=diff
==============================================================================
--- incubator/woden/Site/build/site/dev/1.0/milestoneplan.html (original)
+++ incubator/woden/Site/build/site/dev/1.0/milestoneplan.html Tue Nov 20
07:05:38 2007
@@ -179,10 +179,10 @@
<a href="#M7b+-+August+3%2C+2007">M7b - August 3, 2007</a>
</li>
<li>
-<a href="#M8+-+expected+August+2007">M8 - expected August 2007</a>
+<a href="#M8+-+due+December+2007">M8 - due December 2007</a>
</li>
<li>
-<a
href="#Woden+1.0+-+Date+is+conditional+upon+graduation+from+incubation">Woden
1.0 - Date is conditional upon graduation from incubation</a>
+<a href="#Woden+1.0+-+expected+early+2008">Woden 1.0 - expected early 2008</a>
</li>
<li>
<a href="#Legend">Legend</a>
@@ -553,142 +553,83 @@
</p>
</div>
-<a name="N103E9"></a><a name="M8+-+expected+August+2007"></a>
-<h2 class="boxed">M8 - expected August 2007</h2>
+<a name="N103E9"></a><a name="M8+-+due+December+2007"></a>
+<h2 class="boxed">M8 - due December 2007</h2>
<div class="section">
<p>
- The main objective of the M8 release will be full compliance with the
anticipated
- W3C WSDL 2.0 Recommendation (that is, with the final spec). We expect
the WSDL 2.0 spec
- will move to Proposed Recommendation in April and then to
Recommendation about a month after PR.
- The release date for Woden M8 has not yet been determined.
+ The M8 release will complete Woden's compliance with the W3C WSDL 2.0
Recommendation.
+ The M7 release completed spec-compliance for valid WSDL documents. M8
will complete
+ spec-compliance for invalid WSDL by supporting all of the validation
assertions defined by the
+ Recommendation.
</p>
<p>
- The main objective of Woden M7 was spec-compliance for valid WSDL
documents. The focus for M8 will be
- spec-compliance for invalid WSDL. That is, to complete the validation
functionality in Woden so that
- rule-sequence dependencies and all WSDL 2.0 assertions are fully
supported.
- Woden M8 will also reflect any changes to the WSDL 2.0 spec and test
suite since
- Woden M7's compliance for 'valid' WSDL was established on 10th
February.
- </p>
-<p>
- The priority 1 release-defining criteria for M8 are:
+ The release-defining criteria for M8 are:
</p>
<ul>
<li>to pass all of the 'good' WSDL test cases in the W3C WSDL 2.0 test
suite</li>
<li>to pass all of the 'bad' WSDL test cases in the W3C WSDL 2.0 test
suite</li>
-
-</ul>
-<p>
- Priority 2 criteria for M8 are:
- </p>
-<ul>
-<li>Changes to the extension architecture deferred from M7</li>
+<li>to implement the changes to the extension architecture deferred from
M7</li>
-<li>Any other outstanding API changes</li>
-
+<li>to support validation of WSDL extensions in a way that allows users to
+ provide validation logic for their WSDL extensions.</li>
</ul>
<p>
- See the <a href="http://issues.apache.org/jira/browse/Woden";>Woden
JIRAs</a> marked with Version M8 for a list of
- outstanding function planned for M8.
+ See the <a
href="http://issues.apache.org/jira/browse/WODEN/fixforversion/12312291";>
+ Woden JIRAs to be fixed for Version M8</a> for the remaining
function planned for M8.
+ </p>
+<p>
+ The JIRAs considered part of the release-defining criteria are:
</p>
<ul>
-
-
-<li>WSDL 2.0 Validation JIRAs (Priority 1):
-
- <ul>
-
-<li>WODEN-3 Add component name to Schema-0016 assertion message </li>
-
+
<li>WODEN-39 W3C WSDL2 tests should include assertions </li>
-
+
+<li>WODEN-47 Extensions as generic collections </li>
+
+<li>WODEN-56 Extensions API should not use *internal* classes </li>
+
<li>WODEN-62 Adding an assertion check should be simple </li>
-
+
<li>WODEN-74 Missing QName resolution error for {interface fault} property of
Interface </li>
-
+
<li>WODEN-103 Several binding assertion failures </li>
-
+
<li>WODEN-104 Several import/include assertion failures </li>
-
+
<li>WODEN-105 Several interface assertion failures </li>
-
+
<li>WODEN-106 Several types/schema assertions failures </li>
-
+
<li>WODEN-107 Several qname assertion failures </li>
-
+
<li>WODEN-122 Implement EBNF grammar for {http location} </li>
-
-<li>WODEN-137 QName deserialization test fails on Sun Java 5 JRE </li>
-
-<li>WODEN-149 Use the new WSDL 2.0 assertion numbers <img alt="finished"
height="10" src="../../images/ok.gif" width="10"></li>
-
-</ul>
-
-</li>
-
-
-<li>Other High Priority JIRAs (Priority 2):
-
- <ul>
-
-<li>WODEN-47 Extensions as generic collections </li>
-
-<li>WODEN-56 Extensions API should not use *internal* classes </li>
-
-<li>WODEN-84 Some internally defined constants should be on the API </li>
-
-<li>WODEN-135 Element API, scope of interface and binding fault refs to
include extended interfaces </li>
-
-<li>WODEN-136 Message content model should not be represented in the Element
API </li>
-
-<li>WODEN-138 XML catalog should not need Java system properties </li>
-
-<li>WODEN-141 DescriptionElement.getTypesElement() should not be a factory
method </li>
-
-<li>WODEN-142 <documentation> should not be wrapped as java.lang.Object
</li>
-
-<li>WODEN-147 Entity resolver needed </li>
-
-<li>WODEN-151 WSDL4J license is missing in the release archive files </li>
-
-</ul>
-
-</li>
-
-
-<li>Lower Priority JIRAs:
-
- <ul>
-
-<li>WODEN-32 toString() methods to aid debugging </li>
-
-<li>WODEN-33 DocumentationElement should extend NestedElement <img
alt="finished" height="10" src="../../images/ok.gif" width="10"></li>
-
-<li>WODEN-67 Modularize the build to separate the DOM and OM implementations
</li>
-
-<li>WODEN-115 Support wsdl:description nested within other XML documents </li>
-
-</ul>
-
-</li>
-
-
+
+<li>WODEN-157 SOAP binding reuse of HTTP properties </li>
+
+<li>WODEN-158 SOAPBindingOperationExtensions does not have
isHttpLocationIgnoreUncited </li>
+
</ul>
</div>
-<a name="N10482"></a><a
name="Woden+1.0+-+Date+is+conditional+upon+graduation+from+incubation"></a>
-<h2 class="boxed">Woden 1.0 - Date is conditional upon graduation from
incubation</h2>
+<a name="N10439"></a><a name="Woden+1.0+-+expected+early+2008"></a>
+<h2 class="boxed">Woden 1.0 - expected early 2008</h2>
<div class="section">
<p>
- The initial release of Woden will support DOM parsing and
validation of WSDL 2.0
- documents.
+ The 1.0 release of Woden will support DOM parsing and
validation of WSDL 2.0
+ documents. The main objective of this release will be to
deliver a stable Woden API.
+ That is, a committed API for future releases. User feedback
from the milestone releases
+ so far has resulted in ongoing improvements to the Woden API.
Further work will be required
+ for the 1.0 release to agree the final API.
+ Some <a
href="http://wiki.apache.org/ws/FrontPage/Woden/APIReview";>API review issues</a>
+ have already been caputured on the Woden wiki.
</p>
</div>
-<a name="N1048C"></a><a name="Legend"></a>
+<a name="N10447"></a><a name="Legend"></a>
<h2 class="boxed">Legend</h2>
<div class="section">
<table class="ForrestTable" cellspacing="1" cellpadding="4">
Modified:
incubator/woden/Site/src/documentation/content/xdocs/dev/1.0/milestoneplan.xml
URL:
http://svn.apache.org/viewvc/incubator/woden/Site/src/documentation/content/xdocs/dev/1.0/milestoneplan.xml?rev=596710&r1=596709&r2=596710&view=diff
==============================================================================
---
incubator/woden/Site/src/documentation/content/xdocs/dev/1.0/milestoneplan.xml
(original)
+++
incubator/woden/Site/src/documentation/content/xdocs/dev/1.0/milestoneplan.xml
Tue Nov 20 07:05:38 2007
@@ -248,94 +248,57 @@
</p>
</section>
<section>
- <title>M8 - expected August 2007</title>
+ <title>M8 - due December 2007</title>
<p>
- The main objective of the M8 release will be full compliance with the
anticipated
- W3C WSDL 2.0 Recommendation (that is, with the final spec). We expect
the WSDL 2.0 spec
- will move to Proposed Recommendation in April and then to
Recommendation about a month after PR.
- The release date for Woden M8 has not yet been determined.
+ The M8 release will complete Woden's compliance with the W3C WSDL 2.0
Recommendation.
+ The M7 release completed spec-compliance for valid WSDL documents. M8
will complete
+ spec-compliance for invalid WSDL by supporting all of the validation
assertions defined by the
+ Recommendation.
</p>
<p>
- The main objective of Woden M7 was spec-compliance for valid WSDL
documents. The focus for M8 will be
- spec-compliance for invalid WSDL. That is, to complete the validation
functionality in Woden so that
- rule-sequence dependencies and all WSDL 2.0 assertions are fully
supported.
- Woden M8 will also reflect any changes to the WSDL 2.0 spec and test
suite since
- Woden M7's compliance for 'valid' WSDL was established on 10th
February.
- </p>
- <p>
- The priority 1 release-defining criteria for M8 are:
+ The release-defining criteria for M8 are:
</p>
<ul>
<li>to pass all of the 'good' WSDL test cases in the W3C WSDL 2.0
test suite</li>
<li>to pass all of the 'bad' WSDL test cases in the W3C WSDL 2.0
test suite</li>
+ <li>to implement the changes to the extension architecture
deferred from M7</li>
+ <li>to support validation of WSDL extensions in a way that allows
users to
+ provide validation logic for their WSDL extensions.</li>
</ul>
<p>
- Priority 2 criteria for M8 are:
+ See the <a
href="http://issues.apache.org/jira/browse/WODEN/fixforversion/12312291";>
+ Woden JIRAs to be fixed for Version M8</a> for the remaining
function planned for M8.
</p>
- <ul>
- <li>Changes to the extension architecture deferred from M7</li>
- <li>Any other outstanding API changes</li>
-
- </ul>
<p>
- See the <a href="http://issues.apache.org/jira/browse/Woden";>Woden
JIRAs</a> marked with Version M8 for a list of
- outstanding function planned for M8.
+ The JIRAs considered part of the release-defining criteria are:
</p>
-
<ul>
-
- <li>WSDL 2.0 Validation JIRAs (Priority 1):
-
- <ul>
- <li>WODEN-3 Add component name to Schema-0016 assertion
message </li>
- <li>WODEN-39 W3C WSDL2 tests should include assertions </li>
- <li>WODEN-62 Adding an assertion check should be simple </li>
- <li>WODEN-74 Missing QName resolution error for {interface
fault} property of Interface </li>
- <li>WODEN-103 Several binding assertion failures </li>
- <li>WODEN-104 Several import/include assertion failures </li>
- <li>WODEN-105 Several interface assertion failures </li>
- <li>WODEN-106 Several types/schema assertions failures </li>
- <li>WODEN-107 Several qname assertion failures </li>
- <li>WODEN-122 Implement EBNF grammar for {http location} </li>
- <li>WODEN-137 QName deserialization test fails on Sun Java 5
JRE </li>
- <li>WODEN-149 Use the new WSDL 2.0 assertion numbers <img
src="../../images/ok.gif" height="10" width="10" alt="finished"/></li>
- </ul>
- </li>
-
- <li>Other High Priority JIRAs (Priority 2):
-
- <ul>
- <li>WODEN-47 Extensions as generic collections </li>
- <li>WODEN-56 Extensions API should not use *internal* classes
</li>
- <li>WODEN-84 Some internally defined constants should be on
the API </li>
- <li>WODEN-135 Element API, scope of interface and binding
fault refs to include extended interfaces </li>
- <li>WODEN-136 Message content model should not be represented
in the Element API </li>
- <li>WODEN-138 XML catalog should not need Java system
properties </li>
- <li>WODEN-141 DescriptionElement.getTypesElement() should not
be a factory method </li>
- <li>WODEN-142 <documentation> should not be wrapped as
java.lang.Object </li>
- <li>WODEN-147 Entity resolver needed </li>
- <li>WODEN-151 WSDL4J license is missing in the release archive
files </li>
- </ul>
- </li>
-
- <li>Lower Priority JIRAs:
-
- <ul>
- <li>WODEN-32 toString() methods to aid debugging </li>
- <li>WODEN-33 DocumentationElement should extend NestedElement
<img src="../../images/ok.gif" height="10" width="10" alt="finished"/></li>
- <li>WODEN-67 Modularize the build to separate the DOM and OM
implementations </li>
- <li>WODEN-115 Support wsdl:description nested within other XML
documents </li>
- </ul>
- </li>
-
- </ul>
+ <li>WODEN-39 W3C WSDL2 tests should include assertions </li>
+ <li>WODEN-47 Extensions as generic collections </li>
+ <li>WODEN-56 Extensions API should not use *internal* classes </li>
+ <li>WODEN-62 Adding an assertion check should be simple </li>
+ <li>WODEN-74 Missing QName resolution error for {interface fault}
property of Interface </li>
+ <li>WODEN-103 Several binding assertion failures </li>
+ <li>WODEN-104 Several import/include assertion failures </li>
+ <li>WODEN-105 Several interface assertion failures </li>
+ <li>WODEN-106 Several types/schema assertions failures </li>
+ <li>WODEN-107 Several qname assertion failures </li>
+ <li>WODEN-122 Implement EBNF grammar for {http location} </li>
+ <li>WODEN-157 SOAP binding reuse of HTTP properties </li>
+ <li>WODEN-158 SOAPBindingOperationExtensions does not have
isHttpLocationIgnoreUncited </li>
+ </ul>
</section>
<section>
- <title>Woden 1.0 - Date is conditional upon graduation from
incubation</title>
+ <title>Woden 1.0 - expected early 2008</title>
<p>
- The initial release of Woden will support DOM parsing and
validation of WSDL 2.0
- documents.
+ The 1.0 release of Woden will support DOM parsing and
validation of WSDL 2.0
+ documents. The main objective of this release will be to
deliver a stable Woden API.
+ That is, a committed API for future releases. User feedback
from the milestone releases
+ so far has resulted in ongoing improvements to the Woden API.
Further work will be required
+ for the 1.0 release to agree the final API.
+ Some <a
href="http://wiki.apache.org/ws/FrontPage/Woden/APIReview";>API review issues</a>
+ have already been caputured on the Woden wiki.
</p>
</section>
<section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
