Grzegorz Kossakowski wrote
Yes, agreed but still I cannot help my feeling that such conditionals
are simply a bad idea. Having everything in one place is a benefit of
course but on the other hand I would prefer to use directories or file
name patterns (known from file systems) to distinguish between various,
separate options. That feels much more natural for me.
Then you would still need to have some conditional processing but that
could be a simple Java class that picks up the right resources.
It's maybe a matter of a taste but introduction of any logic to the
configuration is wrong. Configuration should be always declarative not
imperative, IMHO.
Hehe, I actually suggested the same approach to the jetspeed people as
I think it's clearer to have separate files and you just choose at
runtime which files to use. But as you say, it's a matter of taste.
But rereading your use case, I assume that you want to skip whole jar
files, right? So this would be something in the spring configurator of
course.
Yes. At least, I need something that will let me to skip some inclusions
and what should be skipped must be calculated at runtime. That's why I
want to introduce the idea of filter to the Spring Configurator.
Yeah, that's fine.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
