Attendees: Lawrence Mandel, Jeremy Hughes, Graham Turrell, Arthur Ryman, John Kaputin
Minutes
1. Open Action Items - Lawrence Mandel
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-10-17
Lawrence: Has the patch been applied?
Graham: Not yet. There were a few conflicts with head so I have to rework the patch again. The tests patch needs to be updated as well. This should be done this week.
Lawrence: Jeremy, will you review and apply?
Jeremy: Yes. I'll continue to handle this.
2006-09-26 - Jeremy will investigate a method for testing the W3C test suite based on what he did with XmlSchema.
2006-10-17
Jeremy: No status update yet. I think we'll likely use the existing Ant task.
Lawrence: Is there an advantage to reusing Ant?
Arthur: Yes. Ant handles patterns so you don't have to update the script for new tests. Ant also has an error handler that captures the errors. We need to go a step further and check that the correct assertions are being violated for bad test cases and good test cases that violate optional assertions. I expect to do this work before the next interop.
Jeremy: OK. I'll take care of things from the JUnit side.
Closed.
2006-10-03 - John will check to see if there is a Jira open for modularizing the build and open one if it doesn't exist.
2006-10-10
John: Woden-36 is about Mavenizing the build. It's not exactly modularizing except this is required for Maven.
Arthur: Apparently you can run Ant tasks under Maven. Maven build scripts have more structure. I don't think we should force all of our users onto Maven. We should still support Ant.
John: I think we should have a separate Jira to ensure the build is modularized properly then. I'll add a comment to the Jira about modularizing the build and continuing to support Ant. I'll also follow up with someone I know that may be interested in Mavenizing the Woden build.
2006-10-17
John: No update.
2006-10-03 - John will post to the dev list with information about signing releases.
Note: Chinthaka posted the following link after the meeting:
http://wiki.apache.org/ws/FrontPage/Axis2/releases/steps
2006-10-10
John: No status.
2006-10-17
John: Chinthaka posted an Axis wiki page. I found an Apache page that I'll post to the list.
Lawrence: Should we all have keys?
John: Yes. Every artifact that Apache distributes should be signed.
2006-10-03 - Graham will investigate any Apache process that needs to be followed to bundle the W3C WSDL 2.0 schemas with Woden.
2006-10-17
Graham: I sent an e-mail to Dims to get some pointers. I haven't heard back yet.
Jeremy: I've heard a response in the past to talk to legal-discuss. You can also try [EMAIL PROTECTED]
2006-10-10 - Arthur will create instructions for contributing test cases on the W3C WSDL 2.0 working group site.
2006-10-17
Arthur: I started a FAQ and posted the URL to the Woden list. There isn't much in the FAQ yet but as questions are asked it can grow. http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/faq.html
[Action] Lawrence will add the FAQ link to the Woden site.
Closed.
2. Milestone (M7) Status - John Kaputin
John: Chinthaka asked about Woden serialization. We may need to add this to M7.
Lawrence: I think this should be deferred unless it's an absolute requirement for Axis2. We may need to get a resource from Axis2 to help with this work or we'll have to drop some other items from the plan.
3.Development Discussion - All
John: Update on Woden-44 removing the DOM dependencies from the API. I've been refactoring DOMWSDLReader into BaseWSDLReader. This will give us a larger base and reduce the amount of code in each of the two implementations. I'm going to try to get the branch integrated this week. This should have a minimum impact on the programming model.
Lawrence: Our documentation is sparse and getting out of date. We need to update and improve it as we're making changes to Woden.
John: Should we continue to update on the website or cut over to the wiki like Axis and Tuscany?
Jeremy: The advantage of the site is that we can easily bundle the docs with the distribution.
[action] Lawrence will propose moving Woden's documentation to the wiki.
John: I also saw something about using wiki's to author website content. Has anyone seen anything about this?
Arthur: I thought this was possible with wikis. Let's get some content online and then look into this further.
Graham: What's the story with features and properties in the spec?
Arthur: It's hanging on. Canon agreed to get rid of features and properties if we can put in an MTOM extension. This decision should be made on Thursday.
John: If MTOM goes in will that affect the completion time of the spec.
Arthur: I hope not. It may be a separate spec or at least put in another document.
4. Other Business - Open
Lawrence: John, Arthur and I are unavailable next week. I suggest we cancel next week's call.
Next week's status call has been cancelled.
Thanks,
Lawrence Mandel
- Minutes of the Woden Status Telecon, 2006-10-17 Lawrence Mandel
- Re: Minutes of the Woden Status Telecon, 2006-10-1... Eran Chinthaka
- Re: Minutes of the Woden Status Telecon, 2006-... Lawrence Mandel
- Re: Minutes of the Woden Status Telecon, 2... Eran Chinthaka
- Re: Minutes of the Woden Status Teleco... Oshani Seneviratne
