[Dev] Web stuff moved to plugin extension model

[Edmund Grossenbacher]

I just replaced org.ziptie.zap.pax-web with a new plugin, org.ziptie.zap.web that provides an extension point for registering servlets and web filters.  I don't have write access to CVSROOT on the ZipTie CVS server so someone else will have to fix the ziptie CVS alias...  org.ziptie.zap.pax-web is no longer needed.

Rationale:  bundle scanning is a disaster waiting to happen IMO, because it relies on "magical" behavior that is only obvious if you know where to look...  In this case, you would have to know about pax.properties.  This is fine for now, but the more bundle scanning we do the more likely it will be that everyone won't know everything, and eventually people will no longer be aware of the side effects of bundle deployment.

The Eclipse plugin registry seems to provide a uniform way for dealing with this kind of thing.  Extensions points also provide a standardized mechanism for documenting behavior, which was not obvious from pax.properties without looking at the pax-web activator to see what it was searching for in those properties files.

The new extension point supports multiple mappings per servlet / filter.  It uses the HttpService (and pax-web's WebContainer) services to add and remove servlets and filters.  It does not *undeploy* servlets or filters at this time, but neither did pax-web...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20080514/d71dae5a/attachment.html