[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602328#action_12602328
]
Daniel Stucky commented on TUSCANY-2343:
----------------------------------------
Hi,
yes, the activator sets TCCL and I also use option -clean.
The difference is in line 3:
at
org.apache.tuscany.sca.extension.helper.impl.BindingsActivator.start(BindingsActivator.java:72)
(former exception)
vs.
at
org.apache.tuscany.sca.implementation.notification.NotificationModuleActivator.start(NotificationModuleActivator.java:34)
(current exception)
I debugged a little, it happens when Tuscany tries to find the interface
org.apache.tuscany.sca.contribution.processor.StAXArtifactProcessorExtensionPoint.
Perhaps this is somehow related to the problems we encountered with JAXB ?
Bye,
Daniel
> 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, test_bundles.zip
>
>
> 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.
