okay, i've just done the commit which removes most of the old struts1
code, but there is still some work to be done before we can actually
remove the jars and completely wipe our hands of it.
the main offenders are the custom taglibs, which i am happy to get rid
of but we can't because the calendar and menu tags are used in weblog
rendering and basically need to be rewritten as either macros or at
least as non jsp tags. there's a small handful of other places which
still reference struts RequestUtils and things like that as well.
-- Allen
Dave wrote:
On 5/22/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
I was actually just going to suggest this pretty soon :)
sure, i'll go ahead and remove all the old struts1 stuff today.
before i do that though i think i want to reorganize the new struts2
code and jsps so that the structure is not so spread out. so for the
actions i would like to take all of them and unify them under a
roller.ui.struts2.* package naming scheme because that just seems more
appropriate and easier to clearly identify all of the code which makes
up the struts2 UI. the second thing i want to do is subdivide all the
authoring actions into subpackages because currently there are about 50
files in that package and it's making it harder to manage IMO.
i assume nobody would care about this since it's not a functional
change, but if you have a better plan then let me know. with this
change i am basically going to leave 3 fundamental pieces to the
roller.ui package ...
ui.core - code which applies to the web ui as a whole
ui.rendering - weblog rendering code
ui.struts2 - the struts2 ui
Sounds good to me.
- Dave
