----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Sunday, January 16, 2005 10:38 AM
Subject: Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core StandardContext.java
Mark Thomas wrote:FWIW I also did some testing around this on TC5. Multiple services that each contain an engine with the same name creates all sorts of confusion. It behaves as if the same engine is shared by multiple services but I haven't looked at the code yet so I am not 100% sure what is actually going on.
Until I figure out what is going on the work-around (for those few users who might have this setup) is simple - use different names for the each engine.
Yes, there's still redundant data in this area (name on both the engine and service), and not enough checks are done. Engine names must be unique, and should match the associated service name (as at the end, it ends up being used as the JMX domain).
One cleanup area I missed in 5.5 development. I suppose there was far more urgent cleanup to do, and we can now focus on details that were overlooked :)
(but after Yoav tags 5.5.7, thx ;) )
Yes, merging the Engine and the Service would have been a nice cleanup for 5.5, but wasn't as urgent as the other stuff. For example, from the JMX OName point of view, it looks like it should be possible to have multiple Services attached to the same Engine (but you certainly can't have multiple Engines with the same Service).
Given that 5.5 has had a stable release, it's probably not a good idea to do this in that branch. Possibly something for the TC 6 release plan.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
