Date: 2004-03-17T15:33:59
Editor: 212.198.0.93 <>
Wiki: Apache Avalon Wiki
Page: AvalonStandards
URL: http://wiki.apache.org/avalon/AvalonStandards
no comment
Change Log:
------------------------------------------------------------------------------
@@ -174,12 +174,12 @@
* component.logger String Component logger name
* component.id String ID used to locate the component
}}}
-'''Merlin'''
+'''Avalon Meta'''
{{{
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:temp File (directory) temporary directory
urn:avalon:classloader ClassLoader component classloader
}}}
'''Phoenix'''
@@ -197,6 +197,8 @@
|| component classloader || Classloader || {X} || {X} || urn:avalon:classloader ||
Comment from ???: Why not, if the container knows the component's intended
enviroment, map? So if a component that was written for Phoenix asks for app.home,
give it urn:avalon:home.
+
+Comment from Steve: mapping from standard context entries to environment entries is
handled via the Avalon Meta alias attribute as per framework documentation. This
allows a Phoenix component to lookup "app.home" and get back the value corresponding
to the standard "urn:avalon:home" entry.
Comment from leosutic: Sure. That solves backwards compatibility. But it'd be nice to
have one canonical name for the thing, just for the sake of reducing the number of
names for the same thing.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
