You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2010/02/18 09:20:28 UTC
[jira] Created: (FELIX-2093) iPOJO doesn't always use the correct
class loader
iPOJO doesn't always use the correct class loader
-------------------------------------------------
Key: FELIX-2093
URL: https://issues.apache.org/jira/browse/FELIX-2093
Project: Felix
Issue Type: Bug
Components: iPOJO
Affects Versions: iPOJO-1.4.0
Reporter: Richard S. Hall
There are appears to be an issue with nullable object creation, where iPOJO uses the wrong class loader to generate the nullable object for an optional service dependency and this results in the component never getting created. The exact details are a little sketchy to me, but I have shown the example to Clement and he can fill in the details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2093) iPOJO doesn't always use the correct
class loader
Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835153#action_12835153 ]
Clement Escoffier commented on FELIX-2093:
------------------------------------------
The issue comes from the classloader used to create the Nullable object (dynamic proxy).
Currently, we use the bundle classloader which is not necessary correct because it cannot resolve classes used by the service interface that are not imported (the basic solution is to import them).
Using the service interface classloader will fix this issue but break the Nullable interface support (which allows the implementation to detect if the object is a Nullable or not).
> iPOJO doesn't always use the correct class loader
> -------------------------------------------------
>
> Key: FELIX-2093
> URL: https://issues.apache.org/jira/browse/FELIX-2093
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.4.0
> Reporter: Richard S. Hall
> Assignee: Clement Escoffier
>
> There are appears to be an issue with nullable object creation, where iPOJO uses the wrong class loader to generate the nullable object for an optional service dependency and this results in the component never getting created. The exact details are a little sketchy to me, but I have shown the example to Clement and he can fill in the details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2093) iPOJO doesn't always use the correct
class loader
Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier resolved FELIX-2093.
--------------------------------------
Resolution: Fixed
Fix Version/s: iPOJO-1.6.0
Fixed at revision 912323.
> iPOJO doesn't always use the correct class loader
> -------------------------------------------------
>
> Key: FELIX-2093
> URL: https://issues.apache.org/jira/browse/FELIX-2093
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.4.0
> Reporter: Richard S. Hall
> Assignee: Clement Escoffier
> Fix For: iPOJO-1.6.0
>
>
> There are appears to be an issue with nullable object creation, where iPOJO uses the wrong class loader to generate the nullable object for an optional service dependency and this results in the component never getting created. The exact details are a little sketchy to me, but I have shown the example to Clement and he can fill in the details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2093) iPOJO doesn't always use the correct
class loader
Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Clement Escoffier reassigned FELIX-2093:
----------------------------------------
Assignee: Clement Escoffier
> iPOJO doesn't always use the correct class loader
> -------------------------------------------------
>
> Key: FELIX-2093
> URL: https://issues.apache.org/jira/browse/FELIX-2093
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.4.0
> Reporter: Richard S. Hall
> Assignee: Clement Escoffier
>
> There are appears to be an issue with nullable object creation, where iPOJO uses the wrong class loader to generate the nullable object for an optional service dependency and this results in the component never getting created. The exact details are a little sketchy to me, but I have shown the example to Clement and he can fill in the details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2093) iPOJO doesn't always use the correct
class loader
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall closed FELIX-2093.
----------------------------------
> iPOJO doesn't always use the correct class loader
> -------------------------------------------------
>
> Key: FELIX-2093
> URL: https://issues.apache.org/jira/browse/FELIX-2093
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: iPOJO-1.4.0
> Reporter: Richard S. Hall
> Assignee: Clement Escoffier
> Fix For: iPOJO-1.6.0
>
>
> There are appears to be an issue with nullable object creation, where iPOJO uses the wrong class loader to generate the nullable object for an optional service dependency and this results in the component never getting created. The exact details are a little sketchy to me, but I have shown the example to Clement and he can fill in the details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.