Re: Struts Jar File conflict

[Erik Weber]

What I was trying to get at is, can you use separate classloaders? If 
you have an older Servlet app (or some other Java app), and you deploy 
your Struts classes in a different Servlet app, you can (possibly) use 
different versions of your dependency libraries in the two apps because 
the two applications will be loaded by separate classloaders (typically) 
and so will have partitioned namespaces within the JVM. This is assuming 
that you don't put any dependency libraries in the server/container's 
shared classpath(s), which would break the partitioning, and that your 
two applications don't need to exchange (via method calls) instances of 
the dependency classes to communicate.

If you are saying you need to add Struts classes to an existing Servlet 
app, and, say, some of the existing Servlets use older versions of the 
same dependency libraries that Struts requires, I think you are going to 
need to upgrade your older Servlet classes to use the newer versions of 
the dependency libaries. But maybe someone else has a better idea.

Erik
Samuel Cheung wrote:
Erik,
The legacy project is the back end of the application, and Struts is the
front end of the whole servlet application. But the application itself
uses some Jakarta jar (older version than the ones in Struts
distribution).
Any suggestion is welcome.
Thank you.
Sam

-----Original Message-----
From: Erik Weber [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 24, 2005 6:29 PM
To: Struts Users Mailing List
Subject: Re: Struts Jar File conflict

Is the legacy project a servlet app? Can the Struts implementations you 
plan to add exist as a separate servlet app? Can you elaborate on what 
you mean by "use Struts in my legacy project"?

Erik
Samuel Cheung wrote:
 

I have a legacy project which uses some jakarta jar files (e.g.
common.logging.jar) .
And Struts required some jakarta jar files itself.
What if the versions of those 2 jars are different? How can I use
   

Struts
 

in my legacy project? I know one way is to upgrade the legacy project
   

to
 

use the same version as Struts. Is there a better way to do this? I
prefer not to make the drastic changes (risk concern) in order to use
Struts.
Any ideas are welcome.
Thank you.
Sam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

   

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]