On May 2, 2007, at 12:38 , Fabrizio Giustina wrote:
I also think that we should add the "upgrade module" asap, it could be
useful to encorage testing of the 3.1 milestones... do you have
anything ready for that or we could start sketching up something?
Just ideas at the moment, no code.
I *guess* removing a servlet from web.xml would be feasible too,
since we already have a mechanism to add them :)
Well, I actually never liked the fact that we are modifying *files* in
the user webapp like web.xml and repository.xml...
I would not spend a minute in adding a "remove servlet" feature,
leaving the old class as deprecated is enough for me. I would invest
that time in replacing the old servlet that require registration in
web.xml to something nicer (pages? filters? config in jcr?)... I
started this in magnolia 3.0 and we are pretty near to make the single
filter in web.xml the only requirement for magnolia, this would really
simplify upgrading (and integrating magnolia with other
webapps/frameworks)...
True. But we can't keep the deprecated servlets around forever, just
for the sake of giving the user a warning (people upgrading from 3.0
to 3.2 would not see the warning if we remove the servlet post-3.1).
So I'd say either this(removing a deprecated servlet) is automated,
and will then be done by the upgrade mechanism no matter what(i.e not
matter if the upgrade is from 3.0 to 3.1 or 3.2, as all the upgrade
steps will always be taken), or it's not automated and we have a
"manual operation" to be done in the upgrade notes (and the upgrade
notes clearly state that anyone upgrading from X to Z also has to
read the upgrade notes of Y). In both cases and imho, the servlet can
be removed altogether.
Cheers
g
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
