[jboss-jira] [JBoss JIRA] Resolved: (JBCL-169) Support attribute matching from OSGi

[Thomas Diesler (JIRA)]

     [ https://issues.jboss.org/browse/JBCL-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Diesler resolved JBCL-169.
---------------------------------

    Resolution: Out of Date


Out of Date

> Support attribute matching from OSGi
> ------------------------------------
>
>                 Key: JBCL-169
>                 URL: https://issues.jboss.org/browse/JBCL-169
>             Project: JBoss ClassLoader
>          Issue Type: Task
>            Reporter: Thomas Diesler
>            Assignee: Ales Justin
>
> And another thing that needs to happen is to bubble the attribute matching from OSGi to jboss classloading.
> The only reason I originally created OSGi*Capability/Requirement was to implement the attribute matching without modifying
> jboss classloading so it could be used in older versions of jboss5. That restriction was broken by other changes a long time ago.
> We might never have got into this horrible situation if I hadn't done that.
> You should be able to do things like the following in jboss-classloading.xml:
> <capabilities>
>    <package name="foo" attributes="a=b,c=d"/>
> </capabilities>
> <requirements>
>    <package name="bar" match-attributes="(vendor=acme)"/>
> </requirements>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira