Why do you want your classes outside of Tomcat? Copy the classes to
your project when you build and eliminate the dependency. Or better
yet, use a build environment like Ant to do the copying for you. As a
bonus, it'll catch errors before you get to production and the webapp
will be more
Do people read anymore?
As previously stated in the original post, these classes need to be
available to other non-web, non TomCat applications. I do not want to have
to maintain two different repositories. Also as previously stated I have
the desired configuration running on another box but
: Dan [mailto:[EMAIL PROTECTED]
Sent: 01 March 2005 13:55
To: Tomcat Users List
Subject: Re: Need access to classes outside Tomcat for JSPs
Do people read anymore?
As previously stated in the original post, these classes need to be
available to other non-web, non TomCat applications. I do
:56
Subject: RE: Need access to classes outside Tomcat for JSPs
1. Yes people do read, and offer advice based on whether a) they can and b) how
rude the poster is. You fall into (b) right now, so good luck.
2. Tomcat, not TomCat.
3. This is a voluntary user list and you should not expect
help
as you seem to.
-Original Message-
From: Dan [mailto:[EMAIL PROTECTED]
Sent: 01 March 2005 13:55
To: Tomcat Users List
Subject: Re: Need access to classes outside Tomcat for JSPs
Do people read anymore?
As previously stated in the original post, these classes need
List
Subject: RE: Need access to classes outside Tomcat for JSPs
Everybody take it easy. We've all at least thought what
Dan posted, at
one time or another, especially when dealing with Tomcat documentation
(official or otherwise) and the pro-this or pro-that solution folks.
There's
purposes, it's up to you.
Having the same classes twice is no bad thing - having source twice is.
Allistair.
-Original Message-
From: Dan [mailto:[EMAIL PROTECTED]
Sent: 01 March 2005 13:55
To: Tomcat Users List
Subject: Re: Need access to classes outside Tomcat for JSPs
Do
Well, not to be rude, but your design choice is IMHO, poor. Build
tools are available and designed to handle version control -- which is
what I read as the reason for your reluctance to include the classes
directly in the webapp. Every few months, I see someone come on the
list asking what
My apologies for being over the edge, but after pulling my hair out for the
last few days and reading all kinds of web and USENET postings, along with
searching the list archives, I came across all kinds of writings that did
not address the issue of if (and how) this could be done, most just
Just as soon as I hit send
Registry entry.
HKLM | Software | Apache Software Foundation | Procrun 2.0 | Tomcat5 |
Parameters | Java
Classpath =
.;e:\java\library\basic;e:\java\library\custom;E:\java\Tomcat\bin\bootstrap.jar
If you happen to change the bootstrap classpath - please do not email the
list with ClassNotFound issues. ;)
If you really need to access jar's or classes outside of your webapp you can
either:
1) Write your own WebAppClassloader - icky but doable
2) Change
, March 01, 2005 10:37 AM
Subject: Re: Need access to classes outside Tomcat for JSPs
If you happen to change the bootstrap classpath - please do not email the
list with ClassNotFound issues. ;)
If you really need to access jar's or classes outside of your webapp you
can either:
1) Write your own
You could do it that way but I don't feel that placing common resources
in a specific application directory is the proper approach.
For example, if I had shared dlls that are used for Microsoft Office, I
wouldn't place them into the Word application's directory.
At 10:50 AM 3/1/2005, Doug
Classpath problem. Really frustrating.
I'm trying to duplicate a setup on system A to system B and can't get it
working. My problem is when I access the JSP page, Tomcat complains of a
ClassNotFound exception. This happens with all of my custom classes. If I
create a simple JSP page with no
14 matches
Mail list logo