You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2010/02/03 20:49:27 UTC
[jira] Created: (FELIX-2040) Modify framework service registry to
use resolver's new capability/requirement model
Modify framework service registry to use resolver's new capability/requirement model
------------------------------------------------------------------------------------
Key: FELIX-2040
URL: https://issues.apache.org/jira/browse/FELIX-2040
Project: Felix
Issue Type: Improvement
Components: Framework
Affects Versions: felix-2.0.3
Reporter: Richard S. Hall
Assignee: Richard S. Hall
Fix For: felix-3.0.0
The framework's service registry can also benefit from the work being done with the resolver's capability/requirement model. Services can be modeled as capabilities and LDAP filters map directly to requirements. This means the service registry can use the capability indexing mechanism from the resolver to speed up service registry queries in a generic way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2040) Modify framework service registry to
use resolver's new capability/requirement model
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-2040.
----------------------------------
Resolution: Fixed
This is working in trunk and passing the CT.
> Modify framework service registry to use resolver's new capability/requirement model
> ------------------------------------------------------------------------------------
>
> Key: FELIX-2040
> URL: https://issues.apache.org/jira/browse/FELIX-2040
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-2.0.3
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: framework-3.0.0
>
>
> The framework's service registry can also benefit from the work being done with the resolver's capability/requirement model. Services can be modeled as capabilities and LDAP filters map directly to requirements. This means the service registry can use the capability indexing mechanism from the resolver to speed up service registry queries in a generic way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.