tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amy Roh <amy...@apache.org>
Subject Re: [5.0.2] New tag at the end of the week ?
Date Tue, 22 Apr 2003 22:53:34 GMT
>>>> Could you point to the JSR77 section where the mbeans are required 
>>>> to be
>>>> in the same domain ? My understanding so far has been that the 
>>>> domain is
>>>> not specified, and implementations can use it, for example to deal with
>>>> this case, of multiple servlet engine instances running in the same
>>>> j2eeServer, with the same context name and j2eeApplication.
>>>
>>>
>>> If you look at JSR77.3.2, J2EEServer extends J2EEDomain.
>>> J2EEModule(WebModule) and J2EEApplication extend J2EEDeployedObject
>>> which extends J2EEServer.  Therefore, all WebModules that are deployed
>>> under J2EEServer should be in the same J2EEDomain.  When TC is
>>> integrated in AppServer, if multiple engines are created, there isn't a
>>> way for the WebModules to be under same domain.  They'll get deployed
>>> under engine name domain not the J2EEServer, J2EEDomain from the
>>> integration which is not JSR77 compliant.
>>
>>
>>
>> It's not very difficult to fix the creation of WebModule - to move it 
>> under
>> the same domain. 
> 
> 
> When context is created, it inherits its domain name from its parent 
> engine.  If we don't allow multiple engines in one domain, how can we 
> move it under the same domain?

To clarify more...it's not right to distribute managed objects belonging 
to one domain and one server across multiple domain names.  And we're 
doing that if we create more than one engine since we use engine's name 
as its domain for all components under it.

> 
> 
>> The problem is how to figure out what Engine a WebModule belongs to, 
>> if you
>> use JMX ( and embed ) to create it.
>> Attribute is the only solution I can find - and that restricts engines 
>> from registering 2 webmodules with the same name.
> 
> 
> We *should* restrict registering 2 webmodules with the same name, no?
> 
>> The thing I miss is the relation between multiple engines ( and 
>> connectors )
>> and ears. The context name is based on .ear name, server name, and 
>> context
>> name. How do you associate this with an engine ?
>>
>>
>>
>>> What do you think?
>>
>>
>>
>> You have a point with the J2EEDomain. IMO the solution is to fix the
>> WebModule and Servlet registration. If we find how to associate them back
>> to the Engine - it shouldn't be hard to implement.
> 
> 
> with "parentName" (engineName) attribute?  So all we have to change is 
> in WebModule and Servlet to include its parent objectName, right?
> 
> Amy
> 
>>
>> Costin
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message