Duplicate web apps work because they use seperate class loading level.
I'm working on a whitepaper to describe the 3.0 class loading arch
and will post it for comments today or tomorrow.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Dan Christopherson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 17, 2002 8:12 AM
Subject: Re: [JBoss-user] Does JBoss3 have Problems Deploying Similar ejb-
jars in Different EARs


> 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
>
> I've deployed test and production versions of an application on the same
> jboss instance. They're differentiated by the context path of the web
> app and the JNDI names of the ejbs. I need to have different deployment
> descriptors, of course, but I do anyway because security role names and
> datasources change. The advantage over running 2 instances: Apache proxy
> pass rules are simpler, less memory used.
>
> -danch
>
>
> _______________________________________________________________
>
> 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
>


_______________________________________________________________

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