David Jencks wrote:

> On 2002.05.16 20:39:45 -0400 Paul Cody wrote:
> 
>>Wow, I'm really surprised to hear this.  Sorry if this is a stupid
>>question,
>>but what is the benefit of class visibility between hotdeploys?  Stuffing
>>everything into a single classloader namespace seems like a high price to
>>pay.  Any way this 'feature' can be turned off in some sort of
>>'production
>>mode'? 
>>
> 
> It can't be turned off.  In the future we may make it possible to have
> several loader repositories with a parent-child relationship which would
> let you have several versions of a class at once.  However it is not yet
> clear this is cost-effective compared to running several jboss instances.
> 
> The point of having the unified classloaders is that you can redeploy parts
> of your application without taking down the server, and still all calls are
> optimized.  For instance, this lets you split very large applications into
> many ears that can be deployed independently yet have optimized calls
> between ejbs in different ears.  You can remove and redeploy any of the
> ears with different classes without stopping the server.
> 
> Why would you want to have several versions of a class deployed at once? 
> Is this a real use case?
> 
> david jencks
> 
> 
>>Thanks,
>>Paul
>>
>>
[snip to save bandwidth]

Hi David.

Yes, it can be a real use case, if you have several different applications (Ears) 
deployed at once.  The particular case that I have run across (not 
the current project, fortunately) is this;
You have 1 or more jars of common classes (Code reuse is great!)
Fix a bug in 1 class
Test bug fix in one application (Ear file)
As time, load and maintenance schedules permits, deploy fixed jar to other Ears.

For large scale/heavy load systems and better (1000+ users), the above scenario 
generates a real need for separate namespaces for each ear file.  I 
suspect that the above could be handled fairly readily by using a separate Unified 
ClassLoader for each Ear file, or perhaps making an 
EarClassLoader that subclasses the Unified ClassLoader (pass the parent 
UnifiedClassLoader as a constructor parameter?)to be used by the Ear files.

A second scenario that I have seen would be a bit more dicey (Client to remain 
nameless);
Large programming team broken into subteams of 4-5 people each (12-14 teams)
Each team responsible for one application/jar
Team has junior level programmers as team leads
Team makes several "common classes" and sticks them in a package called common
Team makes several "base classes" and sticks them in a package called base
Duplicate over 3 teams
Result: You have at least one or more classes(in this case it was 3-4) with duplicate 
names in duplicate packages in different jar files, but 
everything in the same Ear file.  I think this is one reason why the spec calls for 
different namespaces for each ear file.  Of course, this did not 
show up until they started trying to checkin code into a common repository about 
3/4ths the way through the development cycle.  It helped that all 
the personel for all teams involved were not only in the same country at the time, but 
actually on the same floor of the same building.

-Steve
-- 
Java Developer
Looking for a new job opportunity
214-724-7741




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to