RE: Starting a keel/avalon component/model automatically

One more clarification, this is true only of the webapp-embedded deployment of
Keel.  The distributed Keel servers start the container up as soon as the
server is started.

> Lou/Nate,
> 
> >
> > starts up on the first model access works.
> 
> This is the key.  As it stands now, until at least one model is 
> invoked, the container isn't started up.  Once the container is 
> started, then *all* components with startup activation will be 
> invoked.  One way around that would be to simply write an init 
> servlet, that accesses a harmless model like "nav.navigate" when the 
> container/webapp starts up.
> 
> Shash
> _______________________________________________
> User mailing list
> [email protected]
> http://lists.keelframework.org/listinfo.cgi/user-keelframework.org