The following comment has been added to this issue:
Author:
Created: Wed, 17 Mar 2004 8:15 AM
Body:
The following context entries are defined as part of the standard Avalon Meta package
released by Avalon and published by the PMC as a container independent API and
implementation for meta-info management:
urn:avalon:home
urn:avalon:temp
urn:avalon:partition
urn:avalon:classloader
urn:avalon:name
Components using context entries outside of this scope are application specific. Where
a direct correlection exists - non-compliant components can be migrated or the alias
semantics for context entries (see framework Context spoecification) can be applied.
Where no direct correlation exists, an implementation exists for mapping custom
entries thereby preserving runtime compliance.
I.e. there is not need for a vote because we have already voted at the community and
PMC level. It's defined under Avalon Meta.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=EXLBR-3&page=comments#action_21034
---------------------------------------------------------------------
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 8:15 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]
