Application namespaces (Was Re: [JBoss-user] Does JBoss3 have Problems Deploying Similar ejb- jars in Different EARs)

[Darren H. <da...@ds...>]

I'll jump in on this if I may, as it is a problem that we currently have.  Our 
production environment is striclty controlled, and any new versions of any 
applications have to go through a fairly brutal QA process.  Upgrades must be 
regression tested, as must any dependent apps.  Our applications are layered 
such that we have a very generic common-code layer, with successively less 
generic layers on top.  Our current app-server (not JBoss) uses the standard 
Java classloader, so all apps share the same classpath.  This means that any 
changes to shared code cause screams to echo from the QA team, when they have 
to regression test 20 or more applications.  Their lives (and hence the 
developers') would be made far easier if each app had its own personal 
classloader / namespace.  This would allow us to make changes to common code, 
and introduce the new version into each application separately.

One JVM per application would (for us) mean trying to run 20 or 30 JVM's 
simultaneously per server.  Our support team would shoot us.

Tomcat 4 can already do this, so couldn't JBoss borrow their classloader code, 
in best Open Source tradition?

Regards,

-Darren

On Saturday 18 May 2002 01:39, David Jencks wrote:
> Right now it is certainly harder than it should be to set up many jboss
> instances on the same box, but if it was reasonably easy wouldn't this be a
> safer way to run several applications at once?
>
> david jencks
>
> On 2002.05.17 13:31:08 -0400 Dan Christopherson wrote: