tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 49234] JMX Descriptor Modifications
Date Fri, 06 Aug 2010 05:50:39 GMT

--- Comment #71 from chamith buddhika <> 2010-08-06 01:50:32
EDT ---
(In reply to comment #70)
> (In reply to comment #69)

I am little bit confused here.
> - Start Tomcat

I was under the impression Tomcat should have been already started for MBean
Server to be up and running and to do any work with JMX.

> - Via JMX, select the host
> - Create a new context
> - Configure it to serve content (e.g. from an external directory)
> - Start it

These can be done in one method or using a series of JMX method invocations.
But I guess we can provide the flexibility for both ways. The issue I am having
in order to incorporate these into addChild() is the fact that this method is
common to Engine, Host and Context. But the above steps seem to be specified
towards adding a child (a Context) to a given host. To accommodate that within
addChild we may have to conditionally check for each type of the child (whether
it is a Host or a Context etc.) and take suitable actions (if new Context above
steps or if new Host something else) according to that. It is possible but one
issue that may crop up is different types of children needing different types
of configuration parameters. (e.g: for Context workDir, for Host appBase). May
be we can provide this using a extended MBean classes for different types of
children which overload addChild method with different parameters. WDYT?  

> - Check the content is accessible

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message