On Jul 13, 2006, at 9:36 AM, Jeremy Boynes wrote:
I was thinking of how to load extensions into a chianti runtime and
had the following ideas:
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.
I started working on this and ran into an issue locating the
extension directory. The basic issue is, how does the runtime know
where it is installed?
One technique I've used before is to have a component in the system
that can provide this type of information. This means that other
components can go to one place rather than try and figure it out for
themselves.
I added a RuntimeInfo SPI into the extension stuff to do this. For
now it just returns the install directory (the parent to the boot
directory) but we can add other runtime stuff as needed.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]