felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Sauthier (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FELIX-4111) TypeDeclarations for handlers do not expose namespace (explicitly)
Date Fri, 07 Jun 2013 12:31:20 GMT

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

Guillaume Sauthier reassigned FELIX-4111:

    Assignee: Guillaume Sauthier
> TypeDeclarations for handlers do not expose namespace (explicitly)
> ------------------------------------------------------------------
>                 Key: FELIX-4111
>                 URL: https://issues.apache.org/jira/browse/FELIX-4111
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-runtime-1.10
>         Environment: N/A
>            Reporter: Pierre Bourret
>            Assignee: Guillaume Sauthier
>            Priority: Minor
>         Attachments: FELIX-4111_possible_fix__TypeDeclarations_for_handlers_do_not_expose_namespace_explicitly.patch
> The TypeDeclaration services allows to retrieve the component types that have been declared,
and their current status (bound/unbound , reason, ...)
> However, there is something missing about iPOJO handlers : their TypeDeclaration services
do not allow to retrieve their namespaces. For example, the dependency handler TypeDeclaration.getComponentName()
method returns "requires".
> It would be very appreciable to retrieve the namespace information via the getComponentName()
method (or getComponentNameSpace() ?).
> One possible workaround it to retrieve the namespace from the component metadata :
> String ns = typeDeclaration().getComponentMetadata().getAttribute("namespace");
> It is not very elegant since it relies on iPOJO internals (the metadata structure) and
it returns null for iPOJO core handlers (instead of the "org.apache.felix.ipojo" namespace)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message