On Sat, 2008-09-06 at 11:14 +1000, David Crossley wrote: > Thorsten Scherler wrote: > > > > My initial plan is to reuse the code from whiteboard/dispatcher, conduct > > the needed changes to work with java contracts and add spring support. > > > > Any thoughts. > > When we all talk about "Dispatcher" i thought that we were > talking about the whiteboard/plugins/o.a.f.plugin.internal.dispatcher > That is what i use and what the zone demos use. > > I have never understood what the whiteboard/dispatcher code > is for.
It is the same idea and principals behind it but differently implemented - more efficient. My idea is to create a clean java implementation that can be used standalone and with a wrapper classes in cocoon. > > There is a big concern that i should have raised before. > You have made the STAX jar a dependency, and your > whiteboard/dispatcher/README.txt mentions license issues. Only to include it directly (as add a copy to the lib dir). It is included in the 6.0 jdk but in 1.5 not. I thought about to add ivy support and let ivy resolve it the first time. > Please see the legal-discuss mailing list over the last > couple of years. This has come up a few times, but sorry > i cannot recall the outcome. > > Also see the recent Board report from Apache XML Commons > and their recent mailing lists. > http://wiki.apache.org/xerces/August2008 > They discussed that same problem and added an API > to xml-commons-external. I will have a look at this API rewrite and will preferable use that. Thanks for pointing out. salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
