The following comment has been added to this issue:

     Author: Berin Loritsch
    Created: Wed, 17 Mar 2004 7:56 AM
       Body:
There is no recollection of those context entries being standard.  If they indeed are 
(please have a vote for this), then change the value of the fortress constant that 
refers to the key.  Then add support to handle the old and (now) standard names.
---------------------------------------------------------------------
View this comment:
  
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=EXLBR-3&page=comments#action_21033

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/secure/ViewIssue.jspa?key=EXLBR-3

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: EXLBR-3
    Summary: fortress specific context dependencies
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Avalon Excalibur

   Assignee: 
   Reporter: Stephen McConnell

    Created: Wed, 17 Mar 2004 7:37 AM
    Updated: Wed, 17 Mar 2004 7:56 AM

Description:
Classes such as SourceResolverImpl have runtime dependencies on context entries such 
as "context-root" which is Fortress specific. There are a set of standard Avalon 
context entries:

   urn:avalon:home
   urn:avalon:temp
   urn:avalon:partition
   urn:avalon:classloader
   urn:avalon:name

See constant declarations:
http://avalon.apache.org/meta/api/index.html

Outside of this - custom context entries need to be fully documented and backed with 
appropriate implementation directives (if and where required). 


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to