http://cvs.apache.org/viewcvs.cgi/avalon-excalibur/configuration/src/java/org/apache/excalibur/configuration/merged/ConfigurationMerger.java
ha, this does exactly what I want.. great!
please do note this is not yet a released package ;)
I'm not seeing the use case, but I'm not seeing a problem either :D
Great. One additional question on this one: does the MyClassInSomeExtensionJarWhichMayGetLoadedAtRuntimeALotLater stay loaded or is
there a way to have a "transient" component: just gets initialized(), and then forgotten
about ?
I know of no container which does "automatic unloading" of components, though you can remove components from phoenix through JMX. What you are describing is probably something which you don't want to make a component at all: choose a little bigger granularity, and don't make your "transient" thing an avalon component, but rather something small which is created, managed and destroyed by an avalon component.
More info reg. the use case: consider instead of mimetypes which is kind of a dumb example,
the case of structure/naming conventions for different "entities". What types of entities can exist in the
system depends on what edition(s) of the app is(are) running.. So there's a general registry
that deals with what entities can exists and how they relate to each other, but the actual info about
exactly which entities can exist comes from the edition library. That info exists as simple things
like what entities can be children of what entities, but also has custom classes for each entity that
define what the restrictions on the name of each entity are (all have e.g. isValid(), autoCorrect()
methods). Hope this makes it a little clearer, let me know if not, then I'll try again ;-).
sort-of. I think you need to make sure what you call "entity" and what you call "service". Don't make every swing/gui component into a component; it results in too much overhead. Maybe you want to have a look at jesktop, monarch, or the newest GUI project Berin is working on (info on the dev list, no link ready). Might get you some good ideas for "component granularity".
Thanks a lot for your help, Leo, it's very much appreciated!
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
