tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Sebastien Delfino <jsdelf...@apache.org>
Subject Re: Classloading code in core contribution processing
Date Fri, 22 Feb 2008 17:08:18 GMT
Cut some sections and reordered for readability.
...
 >> Jean-Sebastien Delfino wrote:
 >> - we can use ModelResolvers (1) or bypass them (2)
 >> - ModelResolvers don't handle import cycles and partial packages
 >>
 >> I think that (1) is better. Do you have a use case for cycles and
 >> partial packages right now or can it be fixed later?
...
Rajini Sivaram wrote:
> ContributionTestCase in itest/contribution-classloader contains a test which
> runs into stack overflow if classes are resolved using ModelResolver. I have
> added another test in there for testing for ClassNotFoundException in the
> same scenario. To trigger the failure, you need to modify
> ContributionClassLoader.findClass to use the model resolver of exporting
> contributions to resolve classes instead of their classloader.

Great to see a *test* case for cycles, but my question was: Do you have 
a *use* case for cycles and partial packages right now or can it be 
fixed later?

-- 
Jean-Sebastien

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


Mime
View raw message