Minutes of the Woden Status Telecon, 2006-09-12

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

Present - Oshani, Arthur, John, Jeremy.

We used Arthur's telecon facility.

1. Open Action Items

[action] John to liaise with Chinthaka on when these will be available, how
soon afterwards Woden M6 can be available and confirm that Axis2 will
actually pick up this M6 release of Woden.

[action] Arthur to check on W3C WSDL2 WG timeframe for PR phase and next
interop event and feedback to Woden community.

[action] John to revise an M7 plan (based on original M6 plan), distribute,
then try to finalize at next week's telecon.

[action] John to complete review of Oshani's code in WODEN-44

[action] ALL - review Jeremy's WODEN-40 branch.

[action] John, or others, review Graham's WODEN-14 patch

[action} John circulate his Telecon number for next weeks call.

Deferred, pending other actions:
[action] John will update the M7 plan on the website once finalized.
[action] John will add Oshani to the website's committers list when
updating the M7 plan.

2. Milestone Status

Last week's plan for a Woden M6 release in time for Axis2 1.1 was blocked
on shared dependencies XmlSchema and Axiom. Currently build of SNAPSHOTS or
old releases. Woden M6 should build off the same levels that Axis2 1.1 will
use. Chinthaka has begun release process for XmlSchema and Axiom in prep
for Axis2 1.1 release.

John: Oct 2nd is probably too soon for an M7, especially if we are trying
to release an M6 for Axis2 1.1 which is due 29th Sept. Will propose new
timeframe with revised M7 plan next week, but will likely be late october
at earliest.

Arthur: we need to ensure Axis intend to pick up our M6. Are there any
blocking defects, outstanding requests, etc.
John/Oshani: No, none that we're aware of.


3.Development Discussion - All

WODEN-44 Element Source: Oshani/John agreed, change
ElementSource.getAllElementAttributes back to getAttributes. Consider
whether createElementSource(obj) should be API public on WSDLReader or
whether priv/protected better (depends on who caller is). Also whether to
have an API public noarg createElementSource() similar to
createWSDLSource().
Oshani: is code OK? ready to merge back to trunk yet?
John: I still need to review the 2nd part of WODEN-44 re rolling the Utils
methods into ElementSource impls and how that changes the reader parseXXX
methods.

WODEN-14 URI Resolver: Graham has posted a patch and ask John to look at it
/ open a branch.
John: Anyone who has time can do this, but I will take it as an action
item.
John: If it doesn't impact existing function, maybe better to commit it
straight to Trunk rather than creating another branch (but do this post
M6?)

WODEN-40 Removing the createXXX methods from Description and moving the
'create' behaviour into the addXXX methods spread across the component
model. Nearly complete. Jeremy posted calling for review of this branch and
vote to merge it back to Trunk.
Jeremy: Apache way is to vote for branch to be merged back into TRUNK.


4. Other Business - Open

Oshani can connect over IP using +1 866 prefix, so John will send his
Telecon no. for next week's call (this has 800 and 866 numbers for UK, NA)

W3C test suite - John and Lawrence to focus on this for M7: Lawrence as a
pre-cursor for writing validation logic and John as it may be more suitable
that the large body of outstanding unit tests planned for Woden (i.e.
functional tests will still be created, but in the W3C suite instead).

Arthur led discussion around state of W3C test infrastructure - valid
versus invalid test buckets, test meta-data, test for assertions (errors
for invalid tests, warnings with valid tests), component model interchange
format.

Arthur - discussed possibility of W3C WSDL2 testing to use Schematron to
check validity of component model interchange dump. It provides an enhanced
'schema' for the component model with assertions that may help to find bugs
in implementations.

Oshani: asked about question posted by Graham on if/how to get
xsi:schemaLocation from API.
John: not possible to get this explicitly, but only because requirement has
not yet been considered. Currently probably access it as an ext attribute.
Will read Graham's post and give this some thought.

Discussed need to firm up likely WG timeframe for another Interop,
finalizing CR, moving to PR, etc.
John: would help with Woden planning / priorities.
Arthur: most likely to be towards end of the year.

John: WSDL4J maint release immiment, then should be largely fulltime on
Woden for at least a couple of months. Expect to make good progress. Have
requested from local mgt to focus on finishing off Woden for a couple of
months.

Arthur: Arthur and Lawrence involvement in Woden likely to remain same for
time being. WTP slowing down, but new project starting up, so part-time
only on Woden. Lawrence due back around 20th Sept.

<<end of minutes>>


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