The first idea was to have a directory into which people could
place composites (as jar files or whatever the packaging unit is)
which is scanned by a system service included with the boot
runtime. All the composites found there are used to create
components that are added in to the system composite.
The second was to have a file (probably as XML) that contained a
list of maven artifact ids that corresponded to composites that
could be loaded from a maven repository. There would be a system
service included with the boot runtime that would read this file
and create runtime components from the composites it identified.
Do these seem like reasonable ideas? Any others?
It seems reasonable to have both, as well as a loader to grab composites
from an HTTP endpoint and I'm sure a pile of others - it might be a good
plan to introduce a notion of composite resolution system service which
can be optionally activated at boot time and which can then bootstrap
itself to load a chain of composite resolvers. Or maybe that's cheffing
it up a bit for what's needed :)
--oh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
