Sounds good to me. John Kaputin/UK/[EMAIL PROTECTED] wrote on 16/08/2006 17:29:27:
> > Woden should follow the examples set by other parsers and allow multiple > parser instances to be configured in different ways in the same VM. > > There's a maintenance release of WSDL4J going through now which allows the > WSDLFactory impl classname to be specified via a property file called > javax.wsdl.factory.WSDLFactory in a /META-INF/services directory, allowing > different WSDLFactory implementations to be used in the same VM (e.g. on a > per application basis). I can add similar support to Woden's WSDLFactory > class if agreed (I think there's a TODO comment in the code for it). > > John Kaputin > > > > > Lawrence Mandel > <[EMAIL PROTECTED] > om> To > [email protected] > 15/08/2006 16:50 cc > > Subject > Please respond to Minutes of the Woden Status > [EMAIL PROTECTED] Telecon, 2006-08-15 > he.org > > > > > > > > > > > Attendees: Lawrence Mandel, Graham Turrell > > Minutes > > 1. Open Action Items - Lawrence Mandel > > 2006-08-08 - Graham will follow up with Axis2 to find out a date for their > next release. > 2006-08-15 > Graham: I don't have a specific date yet. I'll post to the axis-dev list > and ask and follow up on woden-dev. > > 2006-08-08 - Other Woden developers should update the team with their > vacation plans for M6 to assist in M6 planning. > Lawrence: I'm away Aug. 28-Sept. 20. > John: I'm away Aug. 10-15, Aug. 28-30. > Graham: I'm away Aug. 21-25. > Jeremy: None. > Arthur: I'm on vacation now, returning for the week of Aug. 14, then out > again Aug. 21-25. > Oshani? > > 2. M6 Status - Lawrence Mandel > > Lawrence: Graham, have you made any progress with the URI resolver? > Graham: I've got a framework in place with a simple URI resolver using a > properties file. There are a few issues such as hard coded XSDs in Woden > but this is mostly working. I'm also working on a resolver for the OASIS > catalog standard to be optionally used. This will require resolver.jar from > xml commons. > Lawrence: Great progress. As a reminder, in Eclipse we will plug in our own > URI resolution framework that supports chaining resolvers and dynamic > binding of new resolvers. Multiple resolvers, chaining, etc. all should be > out of scope for Woden. Woden should simply support the addition of a > single URI resolver that clients can use to do more advanced resolution. > Graham: In order to contribute a resolver a resolver factory needs to be > created and made available anywhere on the classpath. I'll look for > feedback on this mechanism, which I chose for consistency with existing > Woden structure, once I contribute the patch. I'm going to try to get > something out by the end of this week but only if I can get it in a state > that it can be used. > Lawrence: You may have identified a Woden configuration issue. Woden should > follow the examples set by other parsers and allow multiple parser > instances to be configured in different ways in the same VM. As you said, > we'll take a further look at this once you make a patch available. > > 3.Development Discussion - All > > There was no other development discussion. > > 4. Other Business - Open > > There was no other business. > > > Thanks, > > Lawrence Mandel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
