Julian Gosnell wrote:
>
> However, initially, Jetty still expects files, which are best arranged in a
> hierarchy and assosciated with Jetty.
>
>
> Any thoughts....
>
It should not be too much work to do away with the Jetty config files
all together and configure Jetty entirely via JMX.
For the cisco deployment, this is exactly what they do and they have
a JMX configuration architecture not unlike JBosses. The main difference
is that:
+ The lifecycle methods are not expected. (ie don't have to have a
start();
+ Arbitrary methods can be called as well as attributes set.
So I think the aim of the integration, should be to remove all trace of
the jetty configuration mechanism from a standard jboss/jetty installation.
This may be simple? As jetty configuration for most purposes can be
reduced to a series of JMX sets followed by a call to start(). My
vague understanding of the jboss config architecture is that this should
be supported.
However they may be more complex configurations that require arbitrary
methods to be called on the jetty mbeans. These will have to be
addressed either by changing the jetty mbeans so everything can be
done as sets, then start() - or improving the jboss mechanism so that
more arbitrary jmx calls can be made.
Again for the cisco deployment, I used a config file format very similar
to that of Jetty's XML - but which was able to call arbitrary JMX methods.
cheers
--
Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462
Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631
http://www.mortbay.com AU Phone: +61-(0)2 98107029
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
