You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Sauthier (JIRA)" <ji...@apache.org> on 2009/01/14 11:54:59 UTC

[jira] Created: (FELIX-876) Specification auto import is not supported for simple component types

Specification auto import is not supported for simple component types
---------------------------------------------------------------------

                 Key: FELIX-876
                 URL: https://issues.apache.org/jira/browse/FELIX-876
             Project: Felix
          Issue Type: Improvement
    Affects Versions: iPOJO-1.0.0
         Environment: JOnAS 5.1
            Reporter: Guillaume Sauthier


'specification' attributes denotes an interface that needs to be imported (at least its package) in order to allow iPOJO to load the interface.

When you're writing components based on abstract classes, sometimes you ends up with declaring service dependencies for the component that, in fact, belongs to the super class.
If the package used for the dependency's specification is never used in your bundle (containing the concrete class), then you have to manually add an Import-Package.

This is error prone.
iPOJO could check the packages of specifications and auto generate Import-Package for them (if required), just like what's already done for composite components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (FELIX-876) Specification auto import is not supported for simple component types

Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clement Escoffier updated FELIX-876:
------------------------------------

    Component/s: iPOJO

> Specification auto import is not supported for simple component types
> ---------------------------------------------------------------------
>
>                 Key: FELIX-876
>                 URL: https://issues.apache.org/jira/browse/FELIX-876
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.0.0
>         Environment: JOnAS 5.1
>            Reporter: Guillaume Sauthier
>
> 'specification' attributes denotes an interface that needs to be imported (at least its package) in order to allow iPOJO to load the interface.
> When you're writing components based on abstract classes, sometimes you ends up with declaring service dependencies for the component that, in fact, belongs to the super class.
> If the package used for the dependency's specification is never used in your bundle (containing the concrete class), then you have to manually add an Import-Package.
> This is error prone.
> iPOJO could check the packages of specifications and auto generate Import-Package for them (if required), just like what's already done for composite components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (FELIX-876) Specification auto import is not supported for simple component types

Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clement Escoffier resolved FELIX-876.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: iPOJO-1.2.0

Fixed at revision 734402
The 'specification' lookup is now extended to all type of components.


> Specification auto import is not supported for simple component types
> ---------------------------------------------------------------------
>
>                 Key: FELIX-876
>                 URL: https://issues.apache.org/jira/browse/FELIX-876
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.0.0
>         Environment: JOnAS 5.1
>            Reporter: Guillaume Sauthier
>            Assignee: Clement Escoffier
>             Fix For: iPOJO-1.2.0
>
>
> 'specification' attributes denotes an interface that needs to be imported (at least its package) in order to allow iPOJO to load the interface.
> When you're writing components based on abstract classes, sometimes you ends up with declaring service dependencies for the component that, in fact, belongs to the super class.
> If the package used for the dependency's specification is never used in your bundle (containing the concrete class), then you have to manually add an Import-Package.
> This is error prone.
> iPOJO could check the packages of specifications and auto generate Import-Package for them (if required), just like what's already done for composite components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (FELIX-876) Specification auto import is not supported for simple component types

Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clement Escoffier reassigned FELIX-876:
---------------------------------------

    Assignee: Clement Escoffier

> Specification auto import is not supported for simple component types
> ---------------------------------------------------------------------
>
>                 Key: FELIX-876
>                 URL: https://issues.apache.org/jira/browse/FELIX-876
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>    Affects Versions: iPOJO-1.0.0
>         Environment: JOnAS 5.1
>            Reporter: Guillaume Sauthier
>            Assignee: Clement Escoffier
>
> 'specification' attributes denotes an interface that needs to be imported (at least its package) in order to allow iPOJO to load the interface.
> When you're writing components based on abstract classes, sometimes you ends up with declaring service dependencies for the component that, in fact, belongs to the super class.
> If the package used for the dependency's specification is never used in your bundle (containing the concrete class), then you have to manually add an Import-Package.
> This is error prone.
> iPOJO could check the packages of specifications and auto generate Import-Package for them (if required), just like what's already done for composite components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.