"Jung , Dr. Christoph" wrote:
>
> Ok, up to now, I was thinking of relating the application parts of the
> "logical system" via
> relative urls just as Class-Path does: if an app a has url
> <someAbsoluteprefix>/a.jar then you would identify its referenced parent
> <someRelativePrefix>/b.jar as
> canonicalize(<someAbsolutePrefix>/<someRelativePrefix>/b.jar) ...
>
> The problem that I see with a (that�s how I understood your approach)
> statically and globally specified system.xml is that someone must have the
> total
> overview over the complete complex thing before the system is deployed! I�m
> more in favour to let the system.xml emerge from the individual annotations
> in the relevant jars. This allows us, e.g., to dynamically add new
> functionality/component/application to the logical federation at runtime.
I agree with Christoph. If there's a global description of the entire
system, why not just package the whole thing as one EAR? Although I'm
always a little nervous about relying on emergent behaviour - it's like
simulating a flock of birds or something: each bird knows how it should
react to the birds around it and knows how to avoid obstacles and there
is no one bird that has the whole formation mapped out - it just
emerges. Maybe this is cool and maybe it's asking for problems.
Toby.
--
Toby Allsopp
Energy Research Lab
Peace Software International Ltd
Ph +64-9-3730400
