https://issues.apache.org/bugzilla/show_bug.cgi?id=49045
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Catalina |Catalina
Version|unspecified |trunk
Product|Tomcat 6 |Tomcat 7
Target Milestone|default |---
--- Comment #4 from Mark Thomas <ma...@apache.org> 2010-04-07 19:20:00 UTC ---
(In reply to comment #3)
> I will raise a bug for Tomcat 7 as well.
That wasn't quite what I meant. I meant that this bug should be against Tomcat
7, not Tomcat 6. I'll move it.
> Here what I was thinking was since technically a Server can contain more than
> one service that it would be possible to add another service to the server
> associated with the current service component in the MBeanFactory. I will
> change it to throw an exception.
There are cases where there is a service with no server. Hence the exception is
the better option.
> Please correct me if I am wrong here. Since one service is always mapped only
> to one Engine component it would be not possible to use an existing registered
> Engine component with the newly created service without any side effects.
> Hence
> the creation of a brand new engine within the new service. I saw this has been
> done in the removed codes using ServerFactory as well. Another option would be
> that user can seperately create an Engine component prior to Service creation
> and register it and then use it to create the new Service. I will add a
> separate method to create an Engine component in that case.
You are correct that there is a 1 to 1 mapping between service and engine. For
simplicity, I'd still keep them separate.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
