Eric Hancock wrote:
>
> Right, but any product you roll out to a production environment needs some
> kind of management interface. Not necessarily a UI, but hooks to get
> information at runtime, and to shut down / take a server offline.
>
> I could help with this if people think it would be useful.
>
> E -
>
There is something going this direction but help whould be really
appreciated.
Just a couple of lines... James is just a Block so it is avalon that
takes care of blocks lifecycle and managment. this is the main purpose
of the avalon framework: define one entry point and one protocol for
managing all server running on top of it so that server developers (like
us) can forget about boring stuff.
Now if you connect to port 4554 you'll access avalon console where you
can control avalon and its blocks configuration lifecycle etc. As usual
I find hard calling it alfa... :-)
current commands are "stop" "start" "die!" (pretty poor).
One possible path is define a structured managment system on our own,
protocol etc. The other way I'm evaluating is the use of JMX (Sun
standard for managment).
If you are interested or wish to help please subscribe to avalon ML.
Federico Barbieri
<[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
