[
https://issues.apache.org/jira/browse/DOSGI-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823515#comment-13823515
]
David Bosschaert commented on DOSGI-20:
---------------------------------------
bq. Currently we do not have any information about the package version though.
We do actually. It's stored in the endpoint.package.version.<package-name>
property which should be available on the endpoint data. See table 122.1 in the
Remote Service Admin spec...
bq. The problem of choosing the wrong package is not worse than in the dynamic
import case
This approach is certainly not ideal, but I think that the
DynamicImport-Package=* is a lot worse ;) since it can have a lot of nasty side
effects...
bq. I did not think about the other possibility of defering the loadClass. This
also sounds very promising. I will look into both options.
Yeah, the deferring the loadClass option would be ideal if we can get that
working...
> Get rid of the DynamicImport-Package="*"
> ----------------------------------------
>
> Key: DOSGI-20
> URL: https://issues.apache.org/jira/browse/DOSGI-20
> Project: CXF Distributed OSGi
> Issue Type: Bug
> 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 was sent by Atlassian JIRA
(v6.1#6144)
