Attendees: Lawrence Mandel, John Kaputin, Arthur Ryman, Graham Turrell
Minutes
1. Open Action Items - Lawrence Mandel
2006-09-12 - 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.
2006-09-26
John: XmlSchema and Axiom have been released. M6 should be ready. I haven't received confirmation that Axis2 will bundle M6.
2006-10-03
John: Chinthanka has confirmed that Woden M6 will be bundled in Axis2.
Closed.
2006-09-12 - Arthur to check on W3C WSDL2 WG time frame for PR phase and next interop event and feedback to Woden community.
2006-09-26
Arthur: November 13 is the tentative date for the interop event. The likely site is at Canon in France. PR timing looks like June.
John: Jonathan Marsh was going to check with Paul Downing to see if he's interested in participating in the interop event. One possibility is to do a couple days in the UK. Also, Sanjiva and Paul indicated they'd be interested in participating in a European interop event.
2006-10-03
Arthur: Interop is Nov 14-18 at Canon. PR should be by first quarter 2007 with the spec in recommendation phase by second quarter.
Closed.
2006-09-12 - John to complete review of Oshani's code in WODEN-44
2006-09-26
John: I've completed half. More to do.
2006-10-03
John: I'm continuing my review today. I should be complete by next week and have a recommendation.
2006-09-12 - ALL - review Jeremy's WODEN-40 branch.
2006-09-26
John: I reviewed it after it was merged. Looks good to me.
Arthur: Is there an easy way to compare the branch with the trunk?
Jeremy: Yes. In Eclipse. Use compare.
2006-10-03
Closed.
2006-09-12 - John, or others, review Graham's WODEN-14 patch
2006-09-26
Jeremy: I had a look. I spoke with Graham about putting a test together so we can easily test this enhancement.
Graham: No update on the test yet.
2006-10-03
Graham: This patch has not been merged with head yet. Jeremy requested that it only be merged once there was a test case. There is one outstanding problem with the DOM parser. Once that is resolved I'll provide a new patch.
2006-09-26 - Jeremy will investigate a method for testing the W3C test suite based on what he did with XmlSchema.
2006-09-26 - John will investigate the 2 Jiras Arthur's raised for the JUnit failures.
2006-10-03
John: Jeremy had a look.
Arthur: They were dups. The problem was the message labels are optional in XML and required in the component model so you have to apply defaulting rules by looking at the MEP.
John: MEPs have not yet been modelled in Woden. There's some work to do in this area.
Arthur: MEPs should be extensible.
Closed.
2. Milestone (M6/M7) Status - John Kaputin
John: I made a few updates for M6 as per the incubator PMC requests. I'm waiting for another PMC vote. I'll post again if I haven't seen more votes as of tonight to see if we can release with the existing votes.
John: I haven't made any changes to the M7 plan. We should be able to set a publication date now that the interop date has been set. I suggest we plan to do a release by Nov 10. Code freeze on Nov. 6.
Lawrence: I think those dates should work.
John: We should see about splitting up the distribution for M7. I'm not sure if there's a Jira open.
[Action] John will check to see if there is a Jira open for modularizing the build and open one if it doesn't exist.
Lawrence: What's the status of signing the release?
John: There's a page that describes the process.
[Action] John will post to the dev list with information about signing releases.
3.Development Discussion - All
Arthur: Can you provide an overview of the URI resolver patch? How do I contribute a resolver?
Graham: There is a framework for the user to provide their own resolver. A simple resolver that uses a properties file is included to show the use. To add your own resolver you can add an entry to the WSDL properties file, a system property
Arthur: So the key is the URL?
Graham: Yes. Not the namespace.
Arthur: Are these chained.
Graham: No.
Lawrence: Graham and I discussed chaining and following the example of other parsers I suggested we only allow a single resolver to be registered with Woden. Clients should handle chaining.
Arthur: I think this patch should be committed and reviewed in HEAD. I'd like it to be primed with the W3C schemas. The W3C schemas should be redistributed by Woden.
[Action] Graham will investigate any Apache process that needs to be followed to bundle the W3C WSDL 2.0 schemas with Woden.
Arthur: See http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/xmlcatalog/wsdl/
Arthur: Is it possible to add a logger that can log requests that cannot be resolved. This should allow us to ensure we've bundled all the schemas that we need. I'll add a comment to Woden-14.
Arthur: As we go into the interop we may want to contribute assertion checks along with test cases. Is the Woden validator extensible?
Lawrence: Not currently. It's currently structured as a method per assertion to make it easy to understand but there is no way to dynamically extend the validator.
Arthur: It may be useful to dynamically load extension classes so it is easy for people to extend the validator.
Lawrence: We don't want to make every assertion walk the model tree. This leads to serious performance problems as demonstrated by the WS-I test tools.
Arthur: We can create an interface per component and in that way walk the tree once and visit validators along the way.
Lawrence: Let's continue this conversation on the dev list or in a Jira.
4. Other Business - Open
No other business was raised.
Thanks,
Lawrence Mandel
- Minutes of the Woden Status Telecon, 2006-10-03 Lawrence Mandel
- Re: Minutes of the Woden Status Telecon, 2006-10-03 Eran Chinthaka
