On Wednesday 30 July 2008 23:27, Richard Wallace wrote: > It's a bit different than the way the servlet and filter loading works > in the petstore and chronos apps. Instead of having the JettyService go > out and look for instances of those services I renamed it to > JettyServletContainer and had it extend an a ServletContainer interface > with methods to add servlets and filters. I did this mostly in > anticipation of being able to move to an OSGi container at some time in the > (hopefully not too distant) future since this meshes more naturally with > the way you would do it in that environment and will make it almost > trivially easy to implement an OSGiServletContainer or somesuch.
Well, I disagree. OSGi is nowadays advocating the Whiteboard pattern and Extender pattern, both having the central service looking for providers. The argument is the service tracking required is reduced, and the "many" are easier to write than the "few". In fact, we borrow that idea over here. > Just let me spend a bit of time extracting it out of my code base (should > be almost as simple as renaming the package since I've tried to keep things > as loosely coupled as possible) and add in some comments and do other bits > of cleanup and I can either attach it to a message to the list or create an > issue in JIRA and attach it to that. Which do you prefer? We prefer "svn commit" ;-) Everything except Core is open for anyone to commit. Commit rights are granted after registering on JIRA. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
