Minutes of the Woden Status Telecon, 2006-06-13

[Lawrence Mandel]

Attendees: Lawrence Mandel, Samuel Isokpunwu, Eran Chinthaka, Jeremy Hughes, John Kaputin, Graham Turrell
Regrets: Oshani Seneviratne, Arthur Ryman

Minutes

1. Open Action Items - Lawrence Mandel

2006-06-06: Graham will get in touch with Chathura and Oshani to discuss progress and collaboration.
2006-06-13:
Graham: I posted to the Axis and Woden lists a couple times but didn't get any response. I'm going to look at what's open and available in terms of work items and just start to get involved.
Closed.

2006-06-06: John will post to woden-dev with suggested coding conventions.
2006-06-13:
John: I sent out a post this morning.
Jeremy: Eclipse allows these settings to be exported for projects. We should do this for Woden.
Lawrence: I agree. We should support Eclipse. Anyone using another tool is welcome to contribute settings to the Woden repository as well.
John: I'd appreciate the review of the suggestions in my post. The sooner we get a coding convention together the better.
Closed.

2. M5 Status - John Kaputin

Lawrence: Thanks for putting out the vote John. I think we're in good shape. I'm planning on performing the review this afternoon.
John: After the voting period has elapsed on Wed I'll post to the incubator general list calling for the PMC vote.

3. Interoperability Status - Lawrence Mandel

Arthur sent the following status:
1. I extended the Ant task to write a validation report. This will let us compare the Woden results to the expected results for the W3C test suite, both for good and bad documents, i.e. we will be able to easily check that the right assertion violation is reported. [1]

2. Dims reported that there is initial integration in Axis2 with Woden. [2] We should test this. See the JIRA comments for tips on how to test it.

[1] http://lists.w3.org/Archives/Public/www-ws-desc/2006Jun/0044.html
[2] http://issues.apache.org/jira/browse/AXIS2-542

Eran: I've successfully deployed the hotel reservation service to Axis2. I had to update a 2005 URI to 2006 URI. What I did involved an integration layer between Woden and Axis. I'm able to parse the WSDL doc with Woden and create Java artifacts. This is the WSDL2Java tooling. I invoked the operation using a SOAP binding and got the expected response.
John: Was the 2005 URI in the WSDL doc on within Woden?
Eran: WSDL doc.
John: That sounds great. Can you post a summary of what you've done to woden-dev.
Eran: Yes.
[action] Eran to post a summary of the scenario to woden-dev.
John: this will be useful for the interop event in Toronto.
Eran: I may be in Toronto at the interop event. I need a letter from the W3C or IBM Toronto in order to apply for a Visa to attend the event.
Lawrence: I suggest you post to the W3C mailing list and request the letter from the W3C.

Eran: Can someone provide a link to valid WSDL documents?
Lawrence: Sure. There are some in the W3C WSDL test suite. Information is available at [1] and the suite is located at [2]. For [2], look at the documents/good folder.

John: The last time I looked at the comparison results on the W3C site Woden had a lot of red flags. This is still outstanding. I think Arthur is looking at some of them.
Lawrence: I've noticed Arthur has been providing fixes for Ant and posting updates.
John: I'm going to start investigating these red flags for the interop event.

[1] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/index.html
[2] http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/

4. StAX Parser Implementation - Oshani Seneviratne

Lawrence: Oshani passed on her regrets for today's call.

John: The sooner someone can start this the better. The rest of us are pretty busy on other stuff at the moment.
Eran: Oshani has started looking at this already. Already getting some feedback from Chathura.
John: Is she looking at this herself or is someone else working on this as well?
Eran: She's the only one.

5. Other Business - Open

John: There was a discussion last week about the create and add methods on the element API. Should we remove the add elements? The latest proposal from Jeremy is to remove the add methods and just have create methods.
Lawrence: So the create would do the add?
John: Right. Create and add. This removes the ability to create and add it to different parents. This makes sense according to the WSDL 2.0 spec but may not be in the best interest of programmers from an API standpoint. One issue was a common definition (such as common faults) that you want to use in multiple interfaces. We may need to provide a deep copy method as well. I'd appreciate people reviewing this proposal and voting on the suggestions.


Thanks,

Lawrence Mandel