felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "German Vega (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3155) Allow identifying iPojo extensions by a namespace qualified name
Date Tue, 11 Oct 2011 11:59:11 GMT

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

German Vega updated FELIX-3155:

    Comment: was deleted

(was: I have added a patch to propose an implementation of this functionality.

I only modified the ipojo Extender, from version 1.9.0 in the header of the trunk.

I have not fully tested it, or done regression and backward compatibility tests, but seems
 to work in my settings.)
> 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
>         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


View raw message