[ROL-1139] Packaging reorg

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 3.0
• Customer(s): blog.sun.com
• Assignee: Allen T. Gilliland IV
• Reporter: linda skrocki
• Created: 16/May/06 19:58
• Updated: 05/Jan/13 20:46
• Resolved: 21/Jul/06 19:19

Description

i'd like to make a proposal that we do a quick re-org on the presentation layer classes to group them into a set of logical packages based on functionality. these names are just what popped into my head, so that is totally flexible if anyone things they have better names for the packages ...

1. in general, rename roller.presentation.* to roller.ui.<component>.* where we will discuss the components below.

2. the first component will be "core" and will hold any presentation/ui classes that provide functionality to the entire ui layer.

roller.ui.core.util.*
roller.ui.core.filters.*
roller.ui.core.tags.*

util is an obvious inclusion. filters is there because some filters apply to the whole ui layer, like the CharEncodingFilter and PersistenceSessionFilter. and tags.* is there because we allow some jsp tags to be used in multiple components.

3. the second component will be "rendering" and will hold any ui classes that provide functionality for the rendering/displaying of content.

roller.ui.rendering.filters.*
roller.ui.rendering.newsfeeds.*
roller.ui.rendering.search.*
roller.ui.rendering.servlets.*
roller.ui.rendering.velocity.*

this is basically where our Page, Flavor, Search, etc, servlets will go, along with caching filters, etc. anything that is purely about content rendering.

4. the third component will be "publishing" and will hold any ui classes that provide functionality for the publishing/admin process.

roller.ui.publishing.ajax.*
roller.ui.publishing.bookmarks.*
roller.ui.publishing.pings.*
roller.ui.publishing.planet.*
roller.ui.publishing.weblog.*
roller.ui.publishing.website.*

this is all of our struts UI work that manages the admin and editor interfaces for content publishing and site administration. i am actually thinking we could possibly further subdivide this package between publishing.admin.* and publishing.editor.* if we want.

so that's the jest of if. why do this? just because it's nice to have a cleanly organized package structure and i think this makes it easier to separate out the rendering and publishing code.

thoughts? comments?

– Allen