|You might be interested to ry running up the jboss-jetty snapshot I put
|in the binaries module yesterday.
|
|It uses Scott's fix to Service management to allow Jetty's own MBeans to
|coexist with JBoss' in the same JMX agent.
|
|These MBeans publish management interfaces for the objects which contain
|each Servlet/WebApp. You can stop/start and destroy them.
cool. I can see why you don't want these to be init by the JMX
infrastructure. Again though I believe the real "lightweight" solution is
to use the domain scoping of JMX (naming level).. more on that later.
|Is the idea then, to provide a similar binding to objects in JBoss,
|which will publish the internals of the WebContainer ?
at least (as far as I understand the requirement) to have a single way of
getting at the information through the MBean. For example we should be able
to know what webapss are deployed and possibly some metrics on them.
|Jetty does this by creating/destroying MBean facades for these objects
|on the fly (as they are added /removed to/from a BeanContext which
|generates events). This has the advantage that Servlets loaded from a
|Jetty config file have MBeans produced for them, not just WebApps
|created via JBoss' J2EEDeployer.
afaik the deployer doesn't create a MBean per app (we might change that but
for now it isn't there). I do agree that having the individual container
create it's MBean is not only important but probably necessary. I mean that
how is the Mbean to extract the relevant information if it doesn't have a
tight coupling with the container that manages them? On the other hand it
means that we as "integrators" of modules need to make sure that you guys
(as providers of modules) satisfy a couple requirements. The model and the
invocation bus (JMX in our case) seem right to me... does that seem right to
you?
marcf
|
|
|Jules
|
|
|
|
|Scott M Stark wrote:
|
|> The AbstractWebContainer is already in the main branch. I'll look
|> at adding the mgmt. I'm not sure that there is sufficient integration
|> with the web containers to add/remove an individual Servlet, or
|> that they even support such an API. Is this going to be a JMX
|> requirement?
|>
|> >
|> > What is the timeframe for the AbstractWebContainer?
|> >
|> > Right know the requirements are:
|> > - add/remove WebModules (org.jboss.mgt.Module) of the
|> > given application.
|> > - add/remove Servlet (org.jboss.mgt.Servlet) for each
|> > deployed Servlet (and declared JSP page) at the WebModule
|> > (a WebModule would correspondent with a WAR deployment
|> > descriptor or WAR file.
|> >
|> > Right now the classes in org.jboss.mgt are pretty basic and
|> > will be improved on the way to create a management interface.
|> > Therefore feel free to extend this classes.
|> >
|> > For more info have a look at org.jboss.deployment.J2eeDeployer
|> > and org.jboss.ejb.ContainerFactory how it is done for the
|> > EJBs.
|> >
|> > Thanx Andy
|> >
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> http://lists.sourceforge.net/lists/listinfo/jboss-development
|
|
|_________________________________________________________
|Do You Yahoo!?
|Get your free @yahoo.com address at http://mail.yahoo.com
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
