You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by ji...@apache.org on 2004/03/17 16:54:16 UTC
[jira] Commented: (EXLBR-4) resolution of components using /Selector semantics
The following comment has been added to this issue:
Author: Berin Loritsch
Created: Wed, 17 Mar 2004 7:53 AM
Body:
As long as the *Selector interface is part of Avalon Framework, it must be supported. Please note that there is a huge difference between supported and required. The question then becomes what semantics do we want to use to know that we have a Selector that provides components of the type we want for the service interface we have.
In ECM, and consequently in Fortress, appending the name "Selector" to the key was an acceptable practice to guaranteeing that the selector was for the type needed. In Merlin, and consequently the future, how is this going to be guaranteed? Will it require a change to the meta info to know if we want the key accessed as a selector? Perhaps that might be the best solution.
But as long as the selector is part of framework it must be supported.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=EXLBR-4&page=comments#action_21032
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=EXLBR-4
Here is an overview of the issue:
---------------------------------------------------------------------
Key: EXLBR-4
Summary: resolution of components using /Selector semantics
Type: Bug
Status: Unassigned
Priority: Major
Project: Avalon Excalibur
Assignee:
Reporter: Stephen McConnell
Created: Wed, 17 Mar 2004 7:38 AM
Updated: Wed, 17 Mar 2004 7:53 AM
Description:
Involves sorting out where /Selector is really required as opposed to factoring out the use of /Selector in favor of an explicit selection services (which in turn can be implemented with a facility). Some initial actions toward this objective are in place under the merlin/facilities/finder subproject.
---------------------------------------------------------------------
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: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [jira] Commented: (EXLBR-4) resolution of components using /Selector semantics
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thursday 18 March 2004 21:47, Berin Loritsch wrote:
> Which is fine. I am behind that. For now, the selector is part of AF4.
And we declare Merlin = AF5 Reference Container.
Done deal.
Cheerio, old chap!
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [jira] Commented: (EXLBR-4) resolution of components using /Selector
semantics
Posted by Berin Loritsch <bl...@d-haven.org>.
Niclas Hedhman wrote:
> On Wednesday 17 March 2004 23:54, jira@apache.org wrote:
>
>>As long as the *Selector interface is part of Avalon Framework, it must be
>>supported.
>
>
> Simple solution, drop it from the spec.
>
> That is why I like Aaron's original proposal, to move to a AF5 spec base,
> where we cut out all the cruft, such as the Selector.
Which is fine. I am behind that. For now, the selector is part of AF4.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: [jira] Commented: (EXLBR-4) resolution of components using /Selector semantics
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wednesday 17 March 2004 23:54, jira@apache.org wrote:
> As long as the *Selector interface is part of Avalon Framework, it must be
> supported.
Simple solution, drop it from the spec.
That is why I like Aaron's original proposal, to move to a AF5 spec base,
where we cut out all the cruft, such as the Selector.
Niclas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org