Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Leszek Gawron wrote:
Grzegorz Kossakowski wrote:
Leszek Gawron pisze:
SimpleFormInstanceExtractionTransformer.java and
SimpleFormTransformer.java are probably better placed in
cocoon-pipeline-components than cocoon-core. Can I move them ?
What's their use?
At CocoonGT we had some sort of agreement to create optional modules
Please, no more modules. It is bad already as it is - adding *more*
modules only makes it worse. What's wrong with simply deprecating
them, with placing appropriate javadoc?
+1 to move to -components, these are certainly not -core.
But this doesn't solve the problem that many components are loaded
into the spring app context by default.
How's that? These are old school sitemap components. They are not loaded
unless you mention them in your sitemap. What do I miss?
all Avalon component definitions from META-INF/cocoon/avalon are loaded
automatically, unless you use this magic (unknow to me) "readFromClasspath" switch.
Reinhard
Having them into a seperate module makes it easy to exclude them. But
of course than you can run into the situation that you only need one
of them and get them all loaded again :-(
This is the correct assumption for the springified components. It is
just one of the reasons why I use readFromClasspath=false and load only
components / include only files I need.
Vadim
--
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, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
