lingerer huang wrote:
Hi,Sparks
I support your idea totally.Several years ago when I decide to using cocoon
as my application's framework,"Don't need to shutdown when update during
development and deployment" is one majar reason.I like spring ,but when I
update spring I must restart the server,it's painful when developing but it
still acceptable because many developement base on cocoon 2.1 don't need to
In cocoon 2.2,if EVERY css/xsl change need to restart the server,I can
image the developers will kill me if I migrated,maven and rcl is a good
idea,but not all the developers will accept maven and jetty.The mantainer
will kill me twice cause this will make them have a sleepess night every
week only for some style and xsl files changed.
So MY SUGGESTION is : at least provide a non-jar style block implement.What
do you think?
That's already possible: Just use a file: URL in the context path of
your block.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [EMAIL PROTECTED]
________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
