[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600416#action_12600416
]
Georg Schmidt commented on TUSCANY-2343:
----------------------------------------
Thank you for your fast response.
Yes. we are currently using the 5 bundles.
The JIRA issue is in correspondence to the request of the mailing list. This
report just covers one part of the mail conversation. We have had further
information on how to avoid that issue by using version numbers. The
granularity level will help also but the versioning must be correct to be a
real help. For the 2nd issue we will suggest a patch (hopefully soon).
In other case the OSGi environment won't be specific enough and there could
still be class loading issues e.g. with JAXP.
Do I understand well that you are e.g. now using javax.servlet 2.5? Meaning the
correct version of the lib itself (not Tuscany). That would help really much.
How do you define versioning in that case? Open for extension by using lower
bounds or strictly fixed to one version by setting lower and upper bounds.
The question is whether we have the need to modify the build scripts... OSGi
should solve dependent on how you define the version requirements.
Could you explain the issues regarding version numbers on import more exactly?
I did not understood the possible ways you would like to go.
Missing import version numbers could lead to old versions of libraries to be
loaded by Tuscany. e.g. when a just a old version of that lib is present as
OSGi bundle. That should be a general issue. (But it will always depend on
loading behavior of the application)
We would like to use the tuscany-sca-osgi-installer.jar. How did we do that?
(Sorry I am just PM; and getting onto this issue because its vital to me)
> 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
>
> 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.
