From: "Torsten Curdt" <[EMAIL PROTECTED]>
> First off... the replies seem to proove this is a useful feature
> (glad you like the idea :)
It fills a need :-)
> And I now propose to add the CascadingConfiguration to our codebase. If it
> makes it's way into Framework / Excalibur we can easily drop our version.
> We should also add a javadoc comment that this class is borrowed from
> cornerstone and should not be changed!
>
> Here is my +1 for that.
+1
> I'd like to see this feature first before talking about blocks. When we
> start thinking in terms of blocks, applications etc.
+1
> I guess we should
> better try to make cocoon run from within phoenix instead of brewing our
> own stuff. Unfortunately I don't think this will be a peace of cake.
> (haven't yet really used phoenix - so just a wild guess)
Cocoon's ability to run as a Servlet is part of its strength, so it can run
in current servers, but also a weakness sometimes (wanting to go round
Environment abstraction). Running on Phoenix is cool, and IMHO the way to
go, but then, what about the Environment interface? Running not only "in"
but *as* a Phoenix build application could tie it to this specific platform.
Having Tomcat in Phoenix, side by side to Cocoon and James is really cool,
but are people going to use it this way?
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
