[
https://issues.apache.org/jira/browse/CXF-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664145#action_12664145
]
David Bosschaert commented on CXF-1987:
---------------------------------------
That should still be possible without the use of DynamicImport-Package.
Obviously the DSW needs to be able to load classes that it doesn't know in
advance, but by explicitly using the package admin to find the bundle that
exports that class/interface when it needs to construct the bundle, it
localizes this dynamic import. Then it only applies to a very small code
portion rather than the whole bundle.
BTW Peter Kriens suggested that we make this change.
> Get rid of the DynamicImport-Package="*"
> ----------------------------------------
>
> Key: CXF-1987
> URL: https://issues.apache.org/jira/browse/CXF-1987
> Project: CXF
> Issue Type: Improvement
> Components: Distributed-OSGi
> Reporter: David Bosschaert
>
> The current DOSGi implementation uses DynamicImport-Package="*". While this
> is very convenient, it is potentially unpredictable and could have serious
> performance side effects. Therefore it would be better to remove this
> dependency and potentially use direct OSGi API to find the required package
> potentially via the PackageAdmin only when we need to do this type of thing
> i.e. when a proxy is created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
