That's probably what we'll end up doing to preserve backwards compatibility.
And that was my point. :-)
Still, having one name that is the canonical one is nice.
Without it, you wouldn't have a name to which to map. :-)
Gathering all approaches in one place is what we're doing now.
And I'm noticing things like Phoenix has the concept of an application name, but apparently Merlin doesn't, yet.
This is incorrect.
Merlin uses the Avalon Meta package.
The Avalon Meta package defines a set of standard context entries and includes mapping of all Phoenix context names to standard avalon names.
For example, when Merlin is running James it's the Avalon Meta package that is handling the translation between native Avalon Meta names (urn:avalon:...) and Phoenix naming conventions. This is done using alias mappings between standard entries and Phoenix equivalent names. This allows you to lookup "block.name" and "app.name" and get back valid values.
For reference:
Avalon Meta Phoenix alias mapping ------------------------------------------------------- urn:avalon:name block.name urn:avalon:partition app.name urn:avalon:home app.home
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
