[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Schmidt updated TUSCANY-2343:
-----------------------------------
Attachment: Libary Versions.xls
Hi Rajini,
attached you will find a list of libraries (or better a current snapshot [i am
not yet finished]) that we are using in our project.
The list contains version information. Empty fields are not yet analyzed, but a
mismatch would be a potential class loading error.
Further you could find potential issues regarding a class path hell...
The list is not yet completed. But we are using currently more than twice the
amount of bundles. I will work on that over the weekend.
I hope the list gives you a idea what we are currently faceing.
One interesting aspect in this list is that a large amount of these libraries
are axis 2 related.
> 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.
