> -----Original Message-----
> From: Rob Evans (robevans) [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 17, 2003 12:53 PM
> To: 'Avalon framework users'
> Subject: Component deployment, roadmap, and config questions
>
> Folks,
>
> More newbie questions.
>
> 1) How do I deploy and run multiple Merlin components in a single Merlin
> instance.
>
> For example, I have 3 components that perform some sort of JMS
> messaging function and 1 component that provides a JMS connection
> service to the 3 messaging components. I want the 4 components running
> in a single VM. At the moment all I know how to do is run: merlin
> -execute some.package.jar
The easiest way is to simply include all the blocks in one single block.xml
file, or to import them all into one block.xml file:
<container name="tutorial">
<classloader>
<classpath>
<repository>
<resource
id="avalon-framework:avalon-framework-impl"
version="4.1.5"/>
</repository>
</classpath>
</classloader>
<component name="jmsClientOne" class="com.proj.JmsClient"
activation="startup"/>
<component name="jmsClientTwo" class="com.proj.JmsClient"
activation="startup"/>
<component name="jmsClientThree" class="com.proj.JmsClient"
activation="startup"/>
<component name="jmsProvider" class="com.proj.JmsProvider"
activation="startup"/>
</container>
The above scheme would require the clients to declare a dependency on the
provider in order to get the deploy sequence correct.
> 2) Is there a way to configure Merlin so that it will load components on
> the fly?
>
> For example, I'd like to be able to deploy a *new* component into a
> running instance of Merlin.
Not yet. This will probably be easier to do once we have better JMX
support.
> 3) What's the target for having a stable version of Merlin ready for
> production usage and what features will be in that release? I know it's
> hard/impossible for an opensource project to commit to release dates
> but I need to have some indication of marlin's production readiness. We
> are willing to take a little risk but...
We have a release candidate already, but part of the problem is that we
don't have any solid exit criteria. A comprehensive roadmap would help us
all I think (as would JIRA).
J. Aaron Farr
SONY ELECTRONICS
DDP-CIM
(724) 696-7653
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
