You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by Lawrence Mandel <lm...@ca.ibm.com> on 2006/06/13 06:23:27 UTC

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

Attendees: John Kaputin, Lawrence Mandel, Graham Turrell

Minutes

1. Open Action Items - Lawrence Mandel 

There are currently no open action items.

2. M5 Status - John Kaputin 

John: The readWSDL issue is important for Axis for M5. I'll handle this. 
I'm concerned about introducing DOM dependencies in the API.
Lawrence: We had discussed subclassing and creating a DOMWSDLReader.
John: We don't currently have that structure but I think this is the way 
to go.
John: I'm thinking of creating a readWSDL method on WSDLReader that can 
take an object and it's then up to the implementation to understand. I'll 
review the options and go with the appropriate one for M5.

Lawrence: What target are we looking at for M5 at this point? 
John: I'm going to start the approval process tomorrow. I'll update the 
release notes and plan on the website.

John: HTTP binding extensions are a bit of a mess because of the spec 
right now. I've implemented Woden to reflect the current state of the 
spec. This will need to be updated as recommendations are implemented in 
the spec.

3. Interoperability Status - Lawrence Mandel 

Lawrence: Outstanding issues?
John: 2 parts. Woden compliance and integration with Axis. 
WSDL2.0 - parsing logic is pretty much done with HTTP extensions. 
Validation needs to be done for M6. I have noticed component interchange 
formats are showing a lot of red. These failures need to be investigated. 
Equivalence checking is implemented for top level elements. Equivalence 
checking needs to be implemented at other levels.
Equivalence Checking - I've added methods to component interfaces. I can't 
simply override equals method as equivalence is different for elements and 
components. This needs to be fixed before interop event.
Axis2 - Chathura is looking at it. Oshani is also looking at this but not 
I'm not sure if they're working together. I'm hoping Graham can get 
involved as well.
Graham: I put a posting on woden-dev. 
John: A couple weeks ago Chathura suggested looking at Woden serialization 
would be useful. This seems like a longer term item to me. Short term we 
need to get Axis parsing WSDL 2.0 documents. I don't know the specific 
progress.
[action] Graham will get in touch with Chathura and Oshani to discuss 
progress and collaboration.

4. Other Business - Open 

John: There are some mailing list discussions going on around how 
attributes are handled. I'm going to post to woden-dev about agreeing on 
coding conventions. Eclipse changed the formatting of a file that prevents 
diffing.
[action] John will post to woden-dev with suggested coding conventions.
John: Jeremy suggested that anyone that wants to re-format should do two 
commits. First functional changes, then re-format. Formatting changes 
should be done in an isolated way.

John: Jeremy and I will submit the ApacheCon presentation materials today. 
We did an internal dry run last week.
Lawrence: How did it go?
John: Well. Showed that we need to contain the discussion on WSDL 2.0 and 
focus on Woden. Easy at this point to spend too much time about WSDL 2.0. 
We'll post the latest version of the presentation on the Woden website.


Thanks, 

Lawrence Mandel