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

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

Daniel,

Could you run the test through the debugger with breakpoints on the line " 
javax.xml.stream.XMLInputFactory.newInstance(); " in both the cases? When you 
get to this line, could you set breakpoints on the methods "getResource" and 
"findClass" in OSGiBundleActivator.BundleClassLoader? I would like to make sure 
that
   1) The same OSGiBundleActivator$BundleClassLoader object is used in both 
cases
   2) The "bundles" field of this object contains around 200 bundles
   3) getResource("META-INF/services/javax.xml.stream.XMLInputFactory") when 
called returns a valid URL in both cases
   4) findClass("com.ctc.wstx.stax.WstxInputFactory") should get called in both 
cases, and should return a class from the bundle (the first return statement).

Sorry, I really dont have a clue what is broken...

- 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