Stephen wrote:
If the above does not make a lot of sense - please
yell out - this is a question that is getting into one of the more
obscure areas of the Merlin system.
Thanks Stephen for your reply.
And I'm yelling at the top of my voice cause I don't
know even know what to ask now.
LOL - hang in there ...
When u say
You can access another component (the implementation
class) if (a) the
You mean another component in another container, right ?? or what.
Yes.
And what next ?
<container name="top">
<classloader>
<classpath>
<repository>
<resource id="demo:my-common-api" version="1.0">
</repository>
</classpath>
</classloader><!-- We have just created a classloader context in which anything declared under demo:my-common-api is sharable by anything contained in this container. -->
<container name="aaa">
<component name="dog" class="Dog"/>
</container>
<container name="bbb">
<component name="cat" class="Cat">
<dependencies>
<dependency key="a-dog">
<source>./../aaa/dog</source>
</dependency>
</dependencies>
</component></container>
</container>
Cheers, Steve.
Thanks Sonu Vijay
--- Stephen McConnell <[EMAIL PROTECTED]> wrote:
Sonu Vijay wrote:
Hi,
There has been lots of very useful discussion abt
this
topic but I got a question. On the merlin webpage http://avalon.apache.org/merlin/index.html
the diagram shows the Merlin Service Manager interacting with many containers with several components under the containers.
So I want to know, is communication between
components
running in seperate containers:
a)not allowed cause of COP design principals. b)not recommended cause of COP design principals c)not possible in Avalon ( or Merlin specificly )
in
its persent form due to lack of such
functionality.
You can access another component (the implementation
class) if (a) the component in question declares that it should not be
proxied, and (b) the component directive for the consumer explicitly
identifies the source component as the component to be supplied
(using a <dependency><source> statement in the block), and
all component implementation classes are exposed in a classloader
shared by both consumer and provider.
For a service (restricted view of a component) the
above statement holds except that the view of the component is restricted
to the interface defined by the service, and the classes that must be
shared are restricted to those classes exposed by the service
interface.
If the above does not make a lot of sense - please
yell out - this is a question that is getting into one of the more
obscure areas of the Merlin system.
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
