Re: A question regaring Avalon context mappings from Merlin to Avalon

[Siegfried Goeschl]

Hi Stephen, I'm apologize for the sligthly misleading subject - it should read "A question regaring Avalon context mappings from Merlin to Avalon Fortress" .... but my mail client was too quick. My problem is that I'm migrating all of the Fulcrum services to Fortress context names and I got stuck with the "urn:avalon:partition" and "urn:avalon:name". So your answer is potentially definite but it doesn't solve my problem at hand ... :-( Thanks in advance Siegfried Goeschl Stephen McConnell wrote: -----Original Message----- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 11 October 2005 12:34 AM To: Excalibur Developers List Subject: A question regaring Avalon context mappings from Merlin to Avalon Hi folks, looking at +) http://wiki.apache.org/avalon/AvalonStandards +) http://wiki.apache.org/avalon/AvalonContextSurvey there is a mismatch regarding +) urn:avalon:partition ==> component.id or component.logger +) urn:avalon:name ==> component.logger or component.id Is there any definite answer? The partition name was the namespace within which 'name' values were unique, For example a partition named "root/http/context" combined with a component name "pump-handler" can be combined to form the absolute component path "root/http/context/pump-handler". The combination of partition and name results in a unique reference for a deployment scenario and would be an appropriate name for a logging channel for all components sharing the same path (keeping in mind that there exists the possibility for multiple component instances within a given path relative to the lifestyle of the target component (singleton == 1, thread = n, transient = n). /Steve. -------------------------- Stephen McConnell mailto:[EMAIL PROTECTED] http://www.dpml.net