2007/4/13, David H. DeWolf <[EMAIL PROTECTED]>:
I'd personally also like to see us repackage all of the Servlets,
Listeners, Filters, etc. . . into a single web package so that we don't
have on class packages. . .but that's just a personal preference.

Let's organize thoughts then.
The final structure would be:

org.apache.tiles
+-- servlet (to mimic tiles-jsp structure)
     +-- context (context classes)
         +-- ServletTilesContextFactory, etc.
+-- portlet (to mimic tiles-jsp structure)
     +-- context (context classes)
         +-- PortletTilesContextFactory, etc.
+-- web
     +-- startup (Tiles booting classes, help for better name)
         +-- TilesServlet, TilesListener, TilesFilter
     +-- util  (yuk! this deserves a better name!)
         +-- TilesDecorationFilter, TilesDispatchServlet,
              AttributeContextMutator

Obviously the rest remains the same.
This forces the 2.0.3 to be at most an alpha release. Anyway I think
that this refactoring is easy to do and a 2.0.4 can be created quite
quickly.
A second step can be made in 2.1.x, creating different Maven modules
for servlet and portlet technologies.

Thoughts?
Antonio

Reply via email to