You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/01/07 11:25:34 UTC
[jira] Created: (SLING-148) Mark conflicts between package imports
and bootdelegation
Mark conflicts between package imports and bootdelegation
---------------------------------------------------------
Key: SLING-148
URL: https://issues.apache.org/jira/browse/SLING-148
Project: Sling
Issue Type: Improvement
Components: Console
Reporter: Felix Meschberger
Fix For: 2.0.0
Currently the Sling Console lists the packages exported and imported for each bundle on request. In case of a package listed in the org.osgi.framework.bootdelegation property such wiring is actually ignored and the parent class loader is used. This situation might be confusing as the results may be unexpected.
To help in solving possible issues with this problem, wired imports which match any entry in the bootdelegation property should be marked to indicate that respective packages will be loaded from the parent class loader and not from the wired import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-148) Mark conflicts between package
imports and bootdelegation
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559094#action_12559094 ]
Felix Meschberger commented on SLING-148:
-----------------------------------------
The problem is that Rhino selects the PrintWriter.write(int) method when the argument is numeric (which is actually correct, from a certain point of view)...
The fix is to implement a PrintWriter wrapper, which enforces string conversion.
> Mark conflicts between package imports and bootdelegation
> ---------------------------------------------------------
>
> Key: SLING-148
> URL: https://issues.apache.org/jira/browse/SLING-148
> Project: Sling
> Issue Type: Improvement
> Components: Console
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the Sling Console lists the packages exported and imported for each bundle on request. In case of a package listed in the org.osgi.framework.bootdelegation property such wiring is actually ignored and the parent class loader is used. This situation might be confusing as the results may be unexpected.
> To help in solving possible issues with this problem, wired imports which match any entry in the bootdelegation property should be marked to indicate that respective packages will be loaded from the parent class loader and not from the wired import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-148) Mark conflicts between package imports
and bootdelegation
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned SLING-148:
---------------------------------------
Assignee: Felix Meschberger
> Mark conflicts between package imports and bootdelegation
> ---------------------------------------------------------
>
> Key: SLING-148
> URL: https://issues.apache.org/jira/browse/SLING-148
> Project: Sling
> Issue Type: Improvement
> Components: Console
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the Sling Console lists the packages exported and imported for each bundle on request. In case of a package listed in the org.osgi.framework.bootdelegation property such wiring is actually ignored and the parent class loader is used. This situation might be confusing as the results may be unexpected.
> To help in solving possible issues with this problem, wired imports which match any entry in the bootdelegation property should be marked to indicate that respective packages will be loaded from the parent class loader and not from the wired import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-148) Mark conflicts between package imports
and bootdelegation
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-148:
------------------------------------
Comment: was deleted
> Mark conflicts between package imports and bootdelegation
> ---------------------------------------------------------
>
> Key: SLING-148
> URL: https://issues.apache.org/jira/browse/SLING-148
> Project: Sling
> Issue Type: Improvement
> Components: Console
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the Sling Console lists the packages exported and imported for each bundle on request. In case of a package listed in the org.osgi.framework.bootdelegation property such wiring is actually ignored and the parent class loader is used. This situation might be confusing as the results may be unexpected.
> To help in solving possible issues with this problem, wired imports which match any entry in the bootdelegation property should be marked to indicate that respective packages will be loaded from the parent class loader and not from the wired import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-148) Mark conflicts between package imports
and bootdelegation
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-148.
-----------------------------------
Resolution: Fixed
Added interpretation support for the org.osgi.framework.bootdelegation property: Each package in the Export and Import list is checked whether it matches any entry in the bootdelegation property. If so, it is marked with leading exclamation marks, a trailing not and printed in red.
Note, though, the indication that a package is listed in the bootdelegation property does not mean, that classes from these packages will efectively be loaded through the parent class loader: It may still be, that some (or all) classes may be loaded through the wiring if the boot class loader does not have the respective class. This may cause even more problems as some classes of a given package may be loaded from the boot class loader and some from the wiring if the used libraries do not match !
The code to parse the bootdelegation property and compare the package names to the proprty entries is taken from the Apache Felix R4PolicyCore class to match the standard specification behaviour.
Fixed in Rev. 613109
> Mark conflicts between package imports and bootdelegation
> ---------------------------------------------------------
>
> Key: SLING-148
> URL: https://issues.apache.org/jira/browse/SLING-148
> Project: Sling
> Issue Type: Improvement
> Components: Console
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently the Sling Console lists the packages exported and imported for each bundle on request. In case of a package listed in the org.osgi.framework.bootdelegation property such wiring is actually ignored and the parent class loader is used. This situation might be confusing as the results may be unexpected.
> To help in solving possible issues with this problem, wired imports which match any entry in the bootdelegation property should be marked to indicate that respective packages will be loaded from the parent class loader and not from the wired import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.