You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jim Coble <Ji...@duke.edu> on 2002/09/06 21:07:50 UTC
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: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: SSL - cannot find /root/.keystore
Posted by neal <ne...@yahoo.com>.
Actually, I just did a more thorough read of the docs and found the answer.
It's still not working ... but I found the answer to the two questions. :)
-----Original Message-----
From: neal [mailto:nealcabage@yahoo.com]
Sent: Friday, September 06, 2002 1:46 PM
To: Tomcat Users List
Subject: SSL - cannot find /root/.keystore
I'm getting this error while attempting to setup SSL on port 443 on Tomcat
on Linux:
initKeyStore: java.io.FileNotFoundException: /root/.keystore (No such file
or directory)
java.io.FileNotFoundException: /root/.keystore (No such file or directory)
A temporary certificate has been generated and exists in my java/j2sdk/bin
directory. Perhaps these files are suppose to go at the root or something?
But none of these generated files are of type *.keystore. Also, is there an
attribute for the SSL connector where you can specify location of these
docs?
Thanks.
Neal
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
SSL - cannot find /root/.keystore
Posted by neal <ne...@yahoo.com>.
I'm getting this error while attempting to setup SSL on port 443 on Tomcat
on Linux:
initKeyStore: java.io.FileNotFoundException: /root/.keystore (No such file
or directory)
java.io.FileNotFoundException: /root/.keystore (No such file or directory)
A temporary certificate has been generated and exists in my java/j2sdk/bin
directory. Perhaps these files are suppose to go at the root or something?
But none of these generated files are of type *.keystore. Also, is there an
attribute for the SSL connector where you can specify location of these
docs?
Thanks.
Neal
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Best practice advice sought: Classes shared by >1 webapp
Posted by "Josiel S. Oliveira" <si...@uol.com.br>.
> 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.
Hi, Jim.
Why don´t you build a JAR file with the classes to be shared,
and put it in %TOMCAT_HOME%/common/lib directory?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Best practice advice sought: Classes shared by >1 webapp
Posted by Andy Eastham <an...@gliant.com>.
Jim,
If you want the webapps to share the same static values in the same class,
put them in common/classes. (this allows a webapps to affect the data in
another webapp).
If you want the webapps to be totally independent, put a separate copy in
each webapp's individual classes directory.
Or you may want to share some classes and not share others. Put them in the
appropriate place according to the above.
Note: This is because each webapp has it's own class loader, so behaviour is
different to "normal" java programs where static values are shared across
the whole virtual machine.
Hope this helps a bit,
Andy
> -----Original Message-----
> From: Jim Coble [mailto:Jim.Coble@duke.edu]
> Sent: 06 September 2002 20:08
> To: tomcat-user@jakarta.apache.org
> 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:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>