Date: 2004-03-17T11:22:48
Editor: AaronFarr <[EMAIL PROTECTED]>
Wiki: Apache Avalon Wiki
Page: AvalonStandards
URL: http://wiki.apache.org/avalon/AvalonStandards
table makes for easier comparisons -farra
Change Log:
------------------------------------------------------------------------------
@@ -91,6 +91,14 @@
app.home File (directory) persistent directory
}}}
+|| || '''Datatype''' || '''Phoenix''' || '''Fortress''' || '''Merlin''' ||
+|| component name || String || block.name || component.id || urn:avalon:name ||
+|| app/block name || String|| app.name || {X} || urn:avalon:partition ||
+|| app home dir || File || app.home || context-root || urn:avalon:home ||
+|| app temp dir || File || {X} || impl.workDir || urn:avalon:work ||
+|| logger name || String || {X} || component.logger || {X} ||
+|| 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 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]
