Alexis Agahi wrote:
Hi,
When playing with merlin composition: if a service A deals with a service B, it seems that all libs required to make B working should be declared in A block.xml definition (even if the lib are already declared in B block.xml).
That is correct. I a block defitintion references one or services, that block definition must include the appropriate APIs into the classloader of the container that is including the siad services. Also, block B has no idea into what it is being included and cannot know if the entire API suite has been declated in the environment into which it is being introduced. As such, block B has to declare the complete API and implementation classpath.
I might be wrong (since I'm relaying a fact), but I remember having notice this fact.
Simplistic approach would consider that it is not necessary to rewrite the libs declaraion in the "A" block.xml.
If I understand correctly - what your suggesting is that the importing a block would implicity expand the importers classpath to include the APIs of the imported instance. Is that correct?
This would be possible if we explicitly declared an API/SPI/impl seperation in the classloader definition (ummm, has the potential to simplify - but needs more thought).
Stephen.
Cheers
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
