On Thu, 10 Jan 2002 22:55, Stephen McConnell wrote:
> > > Here is your email to me which I have not yet replied to.
> > > (I was swamped by external events at the time and need to get
> > > my head back around this stuff - but not right now - other things
> > > that I have to deal with just at the moment).
kool.
> > However, ....
> > The following (you suggestion) would be "really" useful:
> >
> > void applicationStarting() //before blocks are startedup
> > void applicationStarted() //when all blocks are started up
> > void applicationStopping() //before blocks are shutdown
> > void applicationStopped() //when all blocks are shutdown
> > void applicationFailure() //when application fails to load
> >
> > Providing the application event gives me a hook to (a) the
> > ability to veto application startup and invoke shutdown, and
> > (b) info about the blocks contained in the application. This
> > would let me abandon one of two patches I have on the Avalon/
> > Phoenix stuff.
It will definetly be possible to pass in the meta-info or something similar
and definetly possible to veto startup.
I am less sure about application shutdown and very hesitent to do phoenix
shutdown. One thing I did implement a while ago was that by default if
phoenix contains no active applications (or none being loaded) then it would
shutdown unless a --keep-alive was passed in via command line.
So if I could find a decent mechanism for shutdown of the application it may
be possible to satisfy your needs thusly. I may go have a look at some of
the other similar app kernels and see how they do it.
> And one more little feature - I want to be able to pass an
> argument on the command line when starting Phoenix and have that
> argument passed onto my application listener (but without modifying
> code - i.e. the command line arg could be something like:
>
> -listener net.osm.WayCoolAppListener "wishlist,true"
>
> (Just my little wish list :-) )
This is an interesting question. Most of the J2EE infrastructure (and
friends) require that all "parameters" be specified in some sort of
descriptor or config file. However the desire for this popped up in a few
places and in a JSR I was on. So maybe it would be possible. However in this
case I think the way that it would be done would be to be able to overide
variables that are specified in the config file already.
Anyways that will probably be lower priorty than the BlockListener stuff
--
Cheers,
Pete
-----------------------------------------------------------
Don't take life too seriously --
you'll never get out of it alive.
-----------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
