tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wbchm...@Ensign-BickfordInd.com
Subject RE: Best practice advice sought: Classes shared by >1 webapp
Date Fri, 06 Sep 2002 19:39:13 GMT

We have the same issue.  What we did was seperate them out of the
development into a third project.  In our Tomcat server each webapps has
its own copy of the compiled objects.

We maintain version control on the common objects and upgrade them as we
need to...

(For example, application B is being developed and we make changes to
the common libary if we need to, but dont change app A until it needs
it, or we are upgrading anyway)/




-----Original Message-----
From: Jim.Coble [mailto:Jim.Coble@duke.edu]
Sent: Friday, September 06, 2002 3:08 PM
To: tomcat-user
Subject: Best practice advice sought: Classes shared by >1 webapp


I am developing two web applications that will share a few classes in
common.  What is the best practice for handling this?  Put a copy of the
class in the WEB-INF/classes/ directory structure of both web
applications?
Or put the class in Tomcat's common/classes/ directory structure?  These
common classes are specific to our business, not general purpose ones.
Also, these web applications are for our own internal use only, not ones
that we will bundle up and distribute, though we will need to manage
moving
them successfully from our development server to our production server.

Thanks in advance for any advice on best practices in this situation.
--Jim

==================================
Jim Coble
Senior Technology Specialist
Center for Instructional Technology
Email: jim.coble@duke.edu
Voice: 919-660-5974  Fax: 919-660-5923
Box 90198, Duke University
Durham, NC 27708-0198
==================================



--
To unsubscribe, e-mail:
<mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@jakarta.apache.org>



Mime
View raw message