cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Langham" <mlang...@s-und-n.de>
Subject RE: [RT] user-components.xconf
Date Tue, 05 Mar 2002 08:31:34 GMT
>>
single class) should we adopt the code in out codebase? As much as I hate
duplicate code I also like to see this functionality!
<<
+1

We definately need something like this. I suggest we go for the duplicate
code as it would seem from your message that this is the only way..?

Matthew

--
Open Source Group               sunShine - Lighting up e:Business
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel:+49-5251-1581-30  mlangham@s-und-n.de - http://www.s-und-n.de
           Weblogging at: http://www.need-a-cake.com
=================================================================




-----Original Message-----
From: Torsten Curdt [mailto:tcurdt@dff.st]
Sent: Tuesday, March 05, 2002 9:22 AM
To: cocoon-dev@xml.apache.org
Subject: [RT] user-components.xconf


In order to integrate self-written components we currently only have
user-roles to make these components available to the component manager.
But the configuration of these components still needs to be added to the
cocoon.xconf. This is IMHO dead ugly and bad for upgrade and maintainace
cycles.
We should be able to have a separate configuration besides the
configuration for the core components. We should be able to define a
user.xconf. (or better user-components.xconf?)

I've looked into Avalon but didn't find anything appropriate in Framework
nor Excalibur. In Cornerstone there is a CascadingConfiguration which
could give us easily a working user.xconf. Although I tried a little to
push it does not seem to make it into Excalibur or Framework. So here my
question: instead of having a full Cornerstone jar around (because of this
single class) should we adopt the code in out codebase? As much as I hate
duplicate code I also like to see this functionality!

What do you guys think?
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message