Niclas Hedman wrote:
>
> What JAR file is that? And what is the content of /BLOCK-INF/block.xml
file
> inside?
>
This is the name I assigned to my HelloWorld example.
This is the content of
<!-- definition of an embedded block -->
<container name="merlinj">
<classloader>
<classpath>
<repository>
<resource id="merlinj:merlinj-api" version="1.0"/>
</repository>
</classpath>
</classloader>
<component name="helloworld"
class="org.jemos.avalon.merlin.impl.HelloWorldImpl"
activation="startup">
</component>
<component name="helloclient"
class="org.jemos.avalon.merlin.impl.HelloWorldClient"
activation="startup">
</component>
</container>
>
> No, not necessarily.
> Let's say that component A needs a Service A, so in its code it does the
same
> thing as always, look it up via the ServiceManager.
> But behind the scenes, the container, Merlini(tm), can satisfy that
request by
> providing a remote service instead of a local one.
> So from the components point of view, we should actually be able to
implement
> this transparently. BUT, an "availability" contract is required, since we
> must also handle that the service is no longer available (for whatever
> reason, network problems, reloading of classes...) It is an exciting path
we
> can take for Merlin.
How will the remote service be implemented?
>
> Cheers
> Niclas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
