Attendees: Lawrence Mandel, Arthur Ryman, John Kaputin Regrets: Graham Turrell
Minutes 1. Open Action Items - Lawrence Mandel 2007-01-09 - John to coordinate this change with Axis2 / WSO2 2007-01-16 John: This is the WSDL-120 change, which can't be made by deprecation. I posted to the list today and copies devs from Axis2. I proposed this Thursday to make the change. Jeremy: Axis2 has a woden snapshot from Dec. 12. John: I've asked them to confirm they're using the snapshot and not building from head. 2007-01-23 John: I got a reply from Dims saying that I can make this change. Closed. 2007-01-09 - John to open JIRA to handle WSDL imports correctly (eg: resolving imports with no location attribute) and to check if a testcase exists in the WSDL 2.0 test suite for this (assume not, as if there was one Woden would show a failure). 2007-01-16 John: I haven't opened the Jira yet. 2007-01-23 John: I've opened Woden-124. Closed. 2007-01-16 - Graham will investigate whether the XML catalog spec contains a solution for the resolved location or originating location resolution issue. 2007-01-23 Arthur: I think they should resolve relative to the original location. Lawrence: In WTP the cache resolver does this where the XML catalog resolves relative to the resolved location. John: The URL resolver simply returns a URL, it doesn't return a stream of data. What you're referring to is an entity resolver. [action] Graham and John will discuss this issue further and come up with a proposal to handle dependent documents in the catalog. 2. Milestone (M7) Status - John Kaputin John: Woden-10, 45, 47, 54, 55, 56, 87, 119 should be removed, 120 is close to done, 123 is awaiting resolution, 126, 129 is awaiting resolution. Woden-10 is the last failing test case. I'm also working on Woden-120. I don't think Jan. 29 is realistic for M7 given the number of Jiras left to resolve. I propose we delay a week. That should be long enough to get Woden-10, 45, 87, 120, and 126 done. Lawrence: Can we defer the rest of this list? John: Yes, I think so. Woden-47, 54, 55, and 56 can be deferred. I propose Feb. 5 as the new milestone date. [action]John will post about the new milestone 7 date to the dev list. John: With Woden-10 I had a look at the comments from Michael about Xerces, I think the solution is in an XmlSchema entity resolver. I think we can extract the frag id and use the DOM we have to locate the element. The inputsource takes a binary of text stream. Arthur: You see a fragid on the schema location. You then go back to the document and locate the element. On that element there should be a DOM writer that will print out the element. John: Woden-45 involves updating the Apache boilerplate. This must be done. John: Woden-120 will be done tomorrow. John: Woden-119 I've changed my mind. My proposal is to leave the URL as a string as it is a URL we're interested in and not a URI. John: Woden-87 is fairly straightforward to implement. John: Woden-126 will expose the underlying DOM elements for schemas. John: It would be good to get some up-to-date documentation on the website. 3.Development Discussion - All No other development discussion occurred. 4. Other Business - All John: I think we need to discuss getting Woden out of incubation, soon after M7 if possible. After M7 I'll look at the criteria for graduation and see what's left. Thanks, Lawrence Mandel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
