[snip]
Luciano Resende wrote:
- Another issue I noticed is regarding resolving classReferences.
Because loading a given class would never fails (no class loader
isolation) there is never going to be delegation to the proper
modelResolver from a contribution that is exporting the package. Any
ideas here ? Or should we revisit this when we enhance classLoader
support?
Right, SCA Java imports will only be effective in environments using a
different classloader per SCA contribution, which we have not
encountered yet. I'd suggest to revisit this when we encounter such an
environment. For now adding support for Java import/export only helps
validate the import/export extensibility mechanism.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
