Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 28428 invoked from network); 9 Aug 2002 03:48:57 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Aug 2002 03:48:57 -0000 Received: (qmail 24059 invoked by uid 97); 9 Aug 2002 03:49:23 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 24010 invoked by uid 97); 9 Aug 2002 03:49:22 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 23998 invoked by uid 98); 9 Aug 2002 03:49:21 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) To: tomcat-dev@jakarta.apache.org X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Costin Manolache Newsgroups: gmane.comp.jakarta.tomcat.devel Subject: Re: [PROPOSAL] Have Bootstrap and BootsrapService share startup/shutdown code Date: Thu, 08 Aug 2002 20:45:28 -0700 Lines: 46 Message-ID: References: <3D52E311.20007@apache.org> NNTP-Posting-Host: 12-234-201-54.client.attbi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: main.gmane.org 1028864886 29211 12.234.201.54 (9 Aug 2002 03:48:06 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 9 Aug 2002 03:48:06 +0000 (UTC) User-Agent: KNode/0.7.1 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Remy Maucherat wrote: > BootstrapService never used a port. You're right. I keep confusing the things - I now switched to CatalinaService and it works. BootstrapService depends on daemon - and I don't use daemon to start. ( I hope deamon will switch to introspection ) > Sorry I missed something, but I had the impression that the bootstrap > code was linked with the configuration code. I don't see how we can do > all the changes and add JMX at the core level without doing a new JMX > based launcher (JBoss style, I guess). Maybe I missed something (too > much vacation, I suppose) ;-) Ok. First, I don't think the bootstrap is 'linked' to configuration. The role of bootstrap is to create 2 classloaders, load a class and pass all the params. The only possible configuration would be the location of the server/lib and common/lib - and that could be done using the trick we discuss ( look in the classpath, find the dir ). Having one class with start/stop/main/execute/setters and minimal external deps ( commons-logging and introspection maybe ) should work. The second step is Catalina/CatalinaService. Again, having a single story would be really good. This is the real 'entry point' and should have setters and execute for ant and JMX, as well as main. Regarding JMX - any application can use modeler ( or a similar tool ) and use Catalina.java as a JMX bean. With DynamicMBean it takes one line of code. After that - no need to use any tomcat-specific API, it's just a regular MBean. The configuration is more of an issue after start() is called. If we want to use JMX 'everywhere' ( JBoss style ) or not - that's a different issue. I think it is a good idea, but it needs more discussion and feedback. So far my 'pre-proposal' on configuration got some nodding, but no real feedback or interest. If I'm the only one who has this itch - we can leave server.xml, I won't spend the time implementing something that nobody needs. Costin -- To unsubscribe, e-mail: For additional commands, e-mail: