[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601192#action_12601192
]
Rajini Sivaram commented on TUSCANY-2343:
-----------------------------------------
Sebastian,
Thank you for the update.
Yes, I do now understand that the pdebuild is broken because we are not
converting 3rd party jars into real bundles. They are converted to virtual
bundles when the installer runs, but that obviously does not help with the
pdebuild.
The installer bundle is a temporary solution to enable testing Tuscany under
OSGi. We are still discussing the best way to OSGi-enable Tuscany, and this
feedback from actual usage has been very helpful.
For using the installer bundle at runtime (for now), you can either set
TUSCANY_HOME (the installer looks for jars in TUSCANY_HOME/modules and
TUSCANY_HOME/lib) - you need to update to the latest level of the code.
Alternatively, I can update the code to read the jars relative to the
installer.jar.
I do completely agree that the current installer jar is not suitable for
deployment. I will look through Georg's list to see how much version
constraining we will need for the imports - if they are done in Tuscany.
- Rajini
> OSGi bundle design leads to class loading issues
> ------------------------------------------------
>
> Key: TUSCANY-2343
> URL: https://issues.apache.org/jira/browse/TUSCANY-2343
> Project: Tuscany
> Issue Type: Bug
> Reporter: Georg Schmidt
> Attachments: Libary Versions.xls
>
>
> Currently the design of the OSGi bundles leads to class loading exceptions.
> There seem to be several reasons for this behavior:
> * reexporting of all libraries without version numbers
> * imports without version numbers
> Please use distinct bundles for 3rd party libraries. That would lead to
> easier reusage of your bundles in a larger OSGi project.
> The current status leads to undefined system behaviour due to the OSGi class
> loading concept.
> Please tell if you see a way, how we could support you by achieving this
> goal. (If a solution is interesting for you) We are willing to contribute
> because its a critical project issue for us.
> The problems occur with the current snapshot release. Sorry, I do not know
> which version to take.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
