[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601495#action_12601495
]
Rajini Sivaram commented on TUSCANY-2343:
-----------------------------------------
I have committed some changes to the installer, which should hopefully enable
you to make more progress.
There is some more logic to determine the directory to load Tuscany jars from.
I am hoping that it will now find the jars relative to the installer.jar in
your case. If all else fails, you can set either the environment variable or
the system property TUSCANY_HOME to the directory containing the Tuscany jars.
Please update to the latest itest/osgi-tuscany (again, sorry).
I have added some code in the installer to dump the virtual bundles created by
the installer onto the disk. If you run the maven build in itest/osgi-tuscany
with the environment variable TUSCANY_OSGI_DEBUG set to true, all the 3rd party
libs converted to bundles are written out to the directory containing
tuscany-sca-osgi-installer.jar
(itest/osgi-tuscany/tuscany-osgi-installer/target). Maybe you can copy these to
your Tuscany directory to avoid the pdebuild errors? Tuscany uses these 3rd
party bundles if they are found in the TUSCANY_HOME directory. So I am hoping
that you will be able to use these to isolate versioning/classloading errors.
I had a look at Georg's list of libraries and versioning clashes. Would it be
possible for one of you to send me the third party bundles you are using for
the clashing libraries (either attach to this JIRA or email to [EMAIL
PROTECTED]) ? I would first like to understand the problem with jaxb since the
versions are identical. For the others, where you have different versions, do
you requireTuscany and your application to share classes from these libraries?
What does the "warning" column indicate - do these correspond to actual
classloading errors?
Unfortunately, I might not have time during this week to look into this, but if
you send me the libraries, depending on how complicated it turns out to be, I
will try to respond as soon as I can (I will definitely look at it in the
weekend if I can't get to it earlier). Sorry about that.
- 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.
