[ 
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602583#action_12602583
 ] 

Rajini Sivaram commented on TUSCANY-2343:
-----------------------------------------

Daniel,

It still looks like a problem with TCCL, though I dont know why. I think it is 
too early to be related to the JAXB issue.

Can you add a try-catch block in ScaDomainActivator.initDomainByContribution 
around the code which creates and starts the SCA domain, and include this 
snippet of code twice - just before calling EmbeddedSCADomain.start after you 
have set TCCL, and in the catch block.  

        try {
            System.out.println("TCCL : " + 
Thread.currentThread().getContextClassLoader().getClass());
            javax.xml.stream.XMLInputFactory.newInstance();
        } catch (Throwable e) {
            e.printStackTrace();
        }

I would expect to see the print "TCCL : class 
org.apache.tuscany.sca.osgi.runtime.OSGiBundleActivator$BundleClassLoader" and 
no exception thrown from the call in both cases if it works.

- 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, 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.

Reply via email to