Farr, Aaron wrote:
Hello.
Wow. Even going on a short vacation around here leads to a dangerously
large inbox upon return. :) I'm still working through the avalon-meta
thread. Sounds very good so far. Any idea when it will be safe to play
with? I had a couple enhancements I wanted to add to the meta package in
respect to the Merlin deployment stage extensions.
In the meantime I've started on summarizing the current container supplied context keys. I have Fortress done so far. I'll probably get to Merlin and maybe Phoenix tomorrow:
http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonContextSurvey
Merlin (current):
urn:avalon:partition String partition name urn:avalon:name String component/scenerio name urn:avalon:home File (directory) persistent directory urn:avalon:work File (directory) temproty directory urn:avalon:classloader ClassLoader component classloader
Phoenix:
app.name String application name block.name String component name app.home File (directory) persistent directory
I would like to propose the following as a standard set of context entry name. These names deal with the context entry names that componets should use (i.e. I'm not thinking about container side context keys).
urn:avalon:partition.name -- the partition name in merlin and
the application name in Phoenix
urn:avalon:name -- the deployment scenario name (i.e.
for a singleton this is the component
name or block.name in Phoenix, for other
lifestyles, the name may not be unique
across component instances, but the name
is unique within a single containment
scope)
urn:avalon:home.dir -- a directory that a container
can gaurantee to make available
across JVM sessions (unique per
component that requests it)
urn:avalon:temp.dir -- a directory that is made available
to a component and will be destroy
on JVM termination (unique per
component that requests it)
urn:avalon:classloader -- a classloader for the component
(may not contain any containment
classes)
And why is there no way to get a list of all context values from the Context interface? All we have is get(Object key).
The component declares what it needs in meta. This encorages good SOC bacause the component implementation cannot do navigation or discovery - if it needs something it has to say what it needs and the container has to deal with the supply.
Cheers, Steve.
J. Aaron Farr SONY ELECTRONICS DDP-CIM (724) 696-7653
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
