Summary of Woden Call, 9/15

[John Kaputin <KA...@uk.ibm.com>]

Here's a summary of today's call. Jeremy, John, Lawrence,  Arthur were on
the call.

We reviewed and generally accepted the Milestone plan posted 9/6.
   M1 Sept - Types and Interface parsing, Woden ANT build process.
   M2 Oct - Binding parsing, validation of Types and Interface. Technical
   documentation.
   M3 Nov - Service parsing, validation of Binding. Investigate StAX
   parsing.
   M4 Dec - Service validation. DOM impl complete.
   Need to consider some additional items around M4 (see non-func reqs
   below).
   Lawrence will make some mods and post plan to the Woden website.
   Can be updated with input from Axis as needed

Interested in input from Axis:
   Is milestone plan OK?
   Axis 2 schedule - when is WSDL 2.0 needed?
   is StAX still the strategy?
   ws-commons XmlSchema is currently DOM based - is this a problem?

Need to consider non-functional requirements and including suitable exit
criteria on the Milestone plan:
   determine memory / performance measurements.
   baselining wsdl4j and/or Eclipse WTP wsdl validator to compare against
   Woden performance.
   Eclipse has some EMF-based 1.1-to-2.0 converter. Consider baseling
   against 1.1 docs, converting to 2.0, then comparing against Woden.
   Axis performance reqs for StAX parsing.
   Consider this around Milestone 4 (current priority is functional support
   for WSDL 2.0 to respond to W3C call for implementations)

Release number for first release:
   first planned release will be DOM-based full functional support for WSDL
   2.0 (i.e. to meet the W3C call for implementations)
   We are not sure if this should be a 1.0 or a 0.x release number
   Does the release number depend on incubation status?
   Should the 1.0 release include full Woden objectives (a wsdl 1.1 model,
   1.1-to-2.0 conversion)

Arthur proposed we host a servlet for public to test their WSDL 2.0 docs
using Woden. Hosting to be investigated - W3C have their own serlvet
engine, Eclipse has capability to host servlets, Apache t.b.c.

Arthur is working on tagging the Part 1 spec with assertions that can be
used for validation by WSDL processors (e.g. what to check, error codes,
error messages). Format to be defined for the W3C F2F later in September.

Our testing includes testing Woden against the W3C WSDL 2.0 test suite, so
we should be contributing any new WSDL 2.0 test case documents to the W3C
test suite as we progress.

Outlook.
   Strong focus on Woden over next 3+ months, after some distractions over
   the summer.
   OK for completing M1 coding (John), hoping to complete sufficient
   testing / test cases. Arthur to check if someone from Eclipse is
   available to help with testing.
   M1 usage/technical documentation will be best effort, but lower priority
   than code/test.
   No problems anticipated by John for M2,3 code/test, but need to review
   Part 2 spec in depth (extensions, MEPs) and need to do a maint release
   of wsdl4j during that time.
   Lawrence outlook is good, Eclipse WTP deliverables largely met for time
   being.
   Welcome further help - perhaps on StAX around M3?


regards,
John Kaputin


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