You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Clement Escoffier (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/13 18:49:12 UTC

[jira] [Resolved] (FELIX-3155) Allow identifying iPojo extensions by a namespace qualified name

     [ https://issues.apache.org/jira/browse/FELIX-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clement Escoffier resolved FELIX-3155.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: ipojo-core-1.8.2
         Assignee: Clement Escoffier

Hi,

I've applied the patch. Please check.

Thanks,

Clement
                
> Allow identifying iPojo extensions by a namespace qualified name
> ----------------------------------------------------------------
>
>                 Key: FELIX-3155
>                 URL: https://issues.apache.org/jira/browse/FELIX-3155
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.8.0
>            Reporter: German Vega
>            Assignee: Clement Escoffier
>             Fix For: ipojo-core-1.8.2
>
>         Attachments: Extender.java.patch
>
>
> We want to propose an extension to ipojo and allow our users to mix our components and iPojo core components in the same metatada.
> Unfortunately we use the same name for the type of component.
> This is an example of the kind of metadata we want to support (e.g. using simultaneously iPojo composites and our own ... which happens to have the same factory type name ) :
> <ipojo xmlns="fr.imag.adele.apam" xmlns:ipojo="org.apache.felix.ipojo">
> 	<composite name="S5CompEx" implementation="S5Impl" > ...</composite>
> 	<ipojo:component> .... </ipojo:component>
> 	<ipojo:composite> ....</ipojo:composite>
> 	
> </ipojo>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira