|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Andreas Schaefer
|Sent: Tuesday, May 22, 2001 8:01 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] Call for Help
|
|
|Hi Scott
|
|I had also a closer look at the AbstractWebContainer and saw that
|Jetty already implemented it.
|I think I can go from there and just adjust the deploy() method in the
|AbstractWebContainer (adding the Application Id) and adjust the
|Jetty components.
|
|No, this is not a JMX requirement but finally to add the possibility of
|any management application to get the information about the internals
|of JBoss (what EJB, Servlets, Connectors etc are deployed).

Ok sorry I am getting into the fray with little background.

The JMX requirement you are talking about is probably a "JSR77"
requirement... is that what you mean Scott? (I assume so) in which case the
work that Andy is doing (huh i mean me...) is implementing it.  There will
be requirements placed on the container provide to expose that information
somehow and the simplest way to ensure that is at the JMX layer.  While the
JMX layer won't be a requirement it is the simplest way to ensure that we do
create management domains that follow the model specified in the spec and on
which we have an invocation semantic.

So yes the idea is that the collection tools can have a single way of
getting at the information in the integrated stacks... MBeans are the way to
go.

marc

|
|Andy -)
|----- Original Message -----
|From: "Scott M Stark" <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]>
|Sent: Tuesday, May 22, 2001 4:43 PM
|Subject: Re: [JBoss-dev] Call for Help
|
|
|> 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
|>
|
|
|_______________________________________________
|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

Reply via email to