RE: Starting a keel/avalon component/model

Maxx,

> Hi Shash,
> 
> Hmmm. Doesn't jboss-struts use JBossMQ by default. Mine certainly 
> does. I know this becuase one of my models explicity calls the 
> execute of another model using JMS. I found a class called 
> KeelJmsClientJBossMQ somewhere and used that as a basis for my call.
> 
Admittedly, I haven't used JBossMQ or even the Jboss deployment in a long
time.  But, looking at the ant.properties file for jboss-struts, I am pretty
certain that it does not use JBossMQ.  I would expect at least comm.jbossmq
defined.  You certainly might have created/customized classes to enable the
JBossMQ-based comm., but I don't think kboss-struts uses JBossMQ by default. 
Mike, help me out here, since I am treading ground I normally don't tread. 

> The reason I'm doing this is not to build a distributed system (although
> that may happen in the future), but rather because I need JMS to process
> messages from an external system, struts for the web interface and also
> need to get the whole thing into a single VM.
> 

Then JBossMQ for Keel client-to-server comm. is not needed, you just need
JBossMQ to get input into your system.  Now, you could write a KeelClient
that, instead of input/output via Struts/Cocoon/etc., served Request/Responses
to JBossMQ queue as an option, but looks like you have already solved how to
communicate via JBoss.

> Is there a version of jboss-struts that doesn't use JBossMQ for it's
> internal comms?
>
Unless I am totally confused (which is my default state), I think the question
 should be the other way around: is there a version of JBoss-struts, that does
use JBossMQ? There used to be under the old build-system, but I don't see anb
example deployment for that anymore.
 
> Anyway, my startable model only instantiates on the first struts 
> access to a model and not at server time start.

This is consistent with what I think is happening, you still have what we call
a "direct" client, where instead of JBossMQ and a standalone-server, we are
using the in-memory "channels" to communicate between Keel-client and the
"direct" server (i.e. the server is only started when the client first needs
to  communicate with it).

I think we need Mike to help make sense :-)

Shash