Attendees: Lawrence Mandel, John Kaputin Regrets: Arthur Ryman Minutes
1. Open Action Items - Lawrence Mandel 2007-05-22 - John will follow up with Jeremy about the copyright question in the status file. 2007-06-19 John: Jeremy was following up to ensure the paperwork for our WSDL4J contribution was done. It's with IBM legal now. I'll follow up next week. 2007-06-26 John: I spoke to Jeremy last Tuesday. He's going to confirm that the paperwork from IBM's perspective are complete. 2007-07-10 John: I spoke with Jeremy today. He couldn't get a hold of the legal counsel yet. I'll hopefully have an answer for next week. 2007-07-17 John: Jeremy still hasn't got a response. Lawrence: I spoke with the Apache secretary through e-mail. If we haven't copied any WSDL4J code we may not need an agreement. John: I think we copied some of the common utility code so we should get this agreement in place. 2007-08-07 John: I spoke to Jeremy last week. He still doesn't have an answer yet. 2007-08-14 John: Jeremy has made some progress and hopes to have this completed shortly. 2007-08-21 John: No update. 2007-08-28 John: Still no update. 2007-09-18 John: No progress. 2007-10-02 John: I sent off the required documentation to Apache today. This action should now be complete. Closed. 2007-07-10 - John will look at CodeHaus to try and find the license for the Woodstox jar. 2007-07-17 John: The problem is with the API jar not the wstx jar. I reported this problem on the latest WS board report. Lawrence: There are a couple options. We can follow up with Axiom to see if they've done the due diligence for this library. Two, we can try to move to the Geronimo StAX API but in this case we'll need to ensure Axiom plays well with the Geronimo API. 2007-08-07 John: No progress yet. I'm going to follow up with the Woodstox and Axiom projects to see what they've done to reconcile the license. 2007-08-14 John: I'm about to post to the Apache WS list and will cross post a couple other relevant lists to try and solicit more information. Someone should know how Axis2 redistributes this jar. Lawrence: It was suggested that we use the Geronimo StAX API but I don't think this is an option as Axis2 and Axiom use the StAX API and we don't know what kind of problems this will create. 2007-08-21 John: I sent an e-mail to axis and commons-dev lists today about this. 2007-08-28 John: I didn't get a response from the Axiom developers. I asked whether Axiom would work with the Geronimo API. I'm going to test Woden with the Geronimo jar and if that works I'll suggest to Axiom that they change and see what they think. [action] John will test Woden with the Geronimo API jar. 2007-08-18 John: I dug up an old thread on this that didn't have a resolution. I think the next place to go is legal-discuss. Lawrence: If the test with Geronimo's API jar is successful we should suggest to other projects to test as well. I think it's a better story to reuse code from Apache where possible. 2007-10-02 John: I did some testing with the Geronimo API jar. It works fine with Woden. I'm going to send a note today to ws-commons stating these results and seeing if Axiom can move to the Geronimo API. Axis2 is dependent on the StAX API jar because of Axiom. 2007-05-22 - John will document the Woden decision making and development processes on the Woden site. 2007-06-19 John: No progress. 2007-06-26 John: I'll revisit this in another week after I'm made some further progress on the Woden extensions. 2007-07-10 John: No progress. 2007-07-17 John: No progress. I don't think I'll have a chance to take care of this action this week. 2007-08-07 John: No progress. I think what's needed here is what a new developer would need to get involved. Using Jira and the mailing list. Using the W3C test suite. Open development. Milestones. I haven't had a chance to look at the Apache documentation to see what exactly is required. Lawrence: I'll look at the requirements and put up a skeleton document that we can all work to fill in. 2007-08-14 Lawrence: I posted the skeleton doc last night. Dan: I've started some documentation that I can contribute to this page. 2007-08-21 John: I haven't committed Dan's documentation for build and test yet. I'll probably apply it this week. 2007-08-28 Lawrence: I filled in most of this document. John said he can handle the source code conventions. John: Yes. Tomorrow I'm going to apply Dan's patches including his documentation. Lawrence: Great. Please read through the doc and make any changes you think necessary and this action should be complete. 2007-09-18 John: I've been testing Dan's change to modularize the build. Once I'm done I can commit the changes. Dan: I've included a patch for the XML file from the Web site that contains the updates. 2007-10-02 John: I can't commit Dan's doc updates until I finish the Jira associated with the build changes. I need to review and possibly add to Dan's changes. Lawrence: I reviewed Dan's doc changes and had a couple suggestions, which he's already addressed. The source code section also needs to be filled in. [action] John will fill in the source code section with Java coding conventions. 2007-08-28 - John will test Woden with the Geronimo API jar. 2007-09-18 Dan: I'm going to test this. I'll try to get it done this week. 2007-10-02 John: Done. Woden and Axis2 both functioned correctly with this jar. Closed. 2. Milestone 8 (M8) Status - John Kaputin John: No update. 3. Graduation from Incubation - Lawrence Mandel Lawrence: Two items left. We're making good progress. Just the process documentation, which is almost complete, and the issue with the StAX API jar. 4. Development Discussion - All Lawrence: Ed Merks and Craig Salter voiced concern that the Woden API is too complex. Specifically they both voiced concern about the two layers - component and document, the dependency on XmlSchema, and the use of arrays. John: We can make the schema parser flexible and require casting by the implementation. In Woden's case we would depend on XmlSchema but other implementations can use a different type system. I don't have a convincing argument to keep the element API. The component model itself doesn't seem enough to access all the information required by adopters. If we flatten it into a single API we lose the clarity of the component model, which was a goal of the spec. Lawrence: I think we need to take a look to ensure we're building something useful for adopters. John: WRT lists vs arrays, we can move to Java 5 at this point and make use of typed arrays. Lawrence: Axis2 depends on Java 1.4 or later. See [1]. John: Then I don't think we want to move to lists of objects. We can also create Woden specific collection classes but this adds quite a bit to the API. Let's have the debate on the mailing list and see what the community prefers. John: WRT merging the two models we will need to think about what to do with methods on description in the component and element APIs. Lawrence: I think we should create a page on the wiki detailing these concerns and open a Jira for each where we can have conversations with the community. [action] John will create a page describing the API, XmlSchema, and array concerns and open Jiras for each concern. John: Ed also mentioned something about DOM. Lawrence: AFAIK, the WTP structured source editing (SSE) framework references DOM and EMF handles the reconciliation between changes in DOM and changes in EMF models. John: I looked at Sagara's latest contributions. There was a Java 5 compile error. There are some things to fix with the printed output but he's making good progress. John: I still have 3 or 4 of Dan's Jiras to review and commit. [1]http://ws.apache.org/axis2/1_3/installationguide.html#requirements 5. Other Business - All Lawrence: We couldn't find anyone to speak at ApacheCon US. Lawrence: I think after M8 we need to try to get some information out about Woden. An article would be a good start. If we plan on making some of the major changes we discussed earlier we may want to hold off until those changes are made to avoid adding confusion. Thanks, Lawrence Mandel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
