Re: Classpath problems with tomcat on Linux 9

Figured out my problem. I wasn't placing the class file in a subdirectory of the WEB-INF/classes/. Solution: created UserData.java with package name "userdata" created directory WEB-INF/classes/userdata placed UserData.class in WEB-INF/classes/userdata Thank you all who responded, and a

RE: Classpath problems with tomcat on Linux 9

Hi, You need the <%@ page import="package" %> directive to tell it where to look for it. Yang -Original Message- From: Andy Wadsworth [mailto:[EMAIL PROTECTED] Sent: Monday, April 19, 2004 3:11 PM To: Tomcat Users List Subject: Re: Classpath problems with tomcat on Li

Re: Classpath problems with tomcat on Linux 9

Hi Andy, I'm porting over to TC5 and I've not had any problems with it finding my classes, *BUT* I don't put any classes into the base directory itself, but below that. So for example, my UserBean class is in /WEB-INF/classes/AccessCtrl and it is part of the package "AccessCtrl" (i.e. first

Re: Classpath problems with tomcat on Linux 9

Still no luck. I'm basically trying to do exactly the same thing that the "jsp-examples/checkbox" is doing and I can't get Tomcat to recognize my UserData.class file. I've tried placing my UserData.class file in every location possible, and no luck. My next step will be to downgrade to Tomcat 4 so

RE: Classpath problems with tomcat on Linux 9

I'm guessing you need to put the UserData class in a package, and import it into your savename page. Quoting from JSP 2.0 spec, "As of JSP 2.0, it is illegal to refer to any classes from the unnamed (a.k.a. default) package." -Layton >-Original Message- >From: Andy Wadsworth [mailto:[EMA

Re: Classpath problems with tomcat on Linux 9

Ah, if it was only that simple... The capital "A" is a typo in the email message, not in the actual error. I'm using IE on a WinXP box as my browser, but I sent my email from my Linux machine and I can't copy/paste between the two. -Andy. On Friday 16 April 2004 03:32 pm, Caldarale, Charles R wro

RE: Classpath problems with tomcat on Linux 9

> From: Andy Wadsworth [mailto:[EMAIL PROTECTED] > Subject: Classpath problems with tomcat on Linux 9 > > <...>/work/Catalina/localhost/test/org/apache/jsp/savename_jsp.java:42 > symbol : class UserData > location: class org.apache.jsp.savename_jsp > UserDAta user = null

Re: CLASSPATH problems on 3.3.1

Hey, that is good information! Thank you. I ran them along without quotes for now and all seems to be working. However, I like the other option as well. Michael --- Bill Barker <[EMAIL PROTECTED]> wrote: > Actually, I'm mostly a *nix person. I learned about > "wrapper.jvm.options" > from re

Re: CLASSPATH problems on 3.3.1

Actually, I'm mostly a *nix person. I learned about "wrapper.jvm.options" from reading the comments in the default wrappers.properties file. To save yourself headaches with quotes, "wrapper.jvm.options" can be repeated (and jk_nt_service will concatenate them). So for your example: wrapper.jvm.

RE: CLASSPATH problems on 3.3.1

> -Original Message- > From: Michael Finney [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 11:25 AM > To: Tomcat Users List > Subject: Re: CLASSPATH problems on 3.3.1 > > > So something like this for the wrapper.jvm.options:

Re: CLASSPATH problems on 3.3.1

So something like this for the wrapper.jvm.options: wrapper.jvm.options=-Dorg.apache.tomcat.apps.classpath=C:\SourceW\VSS\src;C:\SourceW\ja\src;C:\SourceW\VSS\lib\xerces.jar;C:\SourceW\lib\xml4j.jar -Xrs right? Can a person use quotes? Did you learn about wrapper.jvm.options from the RELEASE

Re: CLASSPATH problems on 3.3.1

Out of the box, the NT service also ignores your CLASSPATH. You are always free to add "wrapper.classpath" properties to your "wrapper.properties" file to include additional locations in your classpath. Depending on your application, this may or may not result in ClassLoader problems. The other

RE: CLASSPATH problems on 3.3.1

I will look. The NT service form of starting Tomcat does not use start up scripts. Right? I want to make sure I understand what we are saying here about the scripts. --- Larry Isaacs <[EMAIL PROTECTED]> wrote: > Like Tomcat4, Tomcat 3.3's startup scripts ignore > your CLASSPATH. Tomcat 3.2.x'

RE: CLASSPATH problems on 3.3.1

Like Tomcat4, Tomcat 3.3's startup scripts ignore your CLASSPATH. Tomcat 3.2.x's use of the CLASSPATH was one of the top sources of problems. For important differences upgrading from Tomcat 3.2.x to Tomcat 3.3.x, see: For how to configur

Re: Classpath problems

On Tue, 9 Jul 2002, David Goodenough wrote: > Date: Tue, 9 Jul 2002 11:36:46 +0100 > From: David Goodenough <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Classpath problems > > I am having the inevitable initial classpath problems setti

RE: Classpath problems

Howdy, The simplest way: look into server.xml, change all debug="0" to debug="99". This will get more info than you probably want, but that's (usually) a good thing when debugging ;) As an aside: classpath problems typically don't require that much debugging information. If you get a class not

RE: Classpath problems with Tomcat4 and RedHat 7.2

--- Jose Ferrer <[EMAIL PROTECTED]> wrote: > Yes, CATALINA_HOME is set to /var/tomcat4 > > Here is my simple jsp > > <%@ page language="java" %> > <%@ page import = "java.util.*" %> > <%@ page import = "java.io.*" %> > <%Propertie

RE: Classpath problems with Tomcat4 and RedHat 7.2

Yes, CATALINA_HOME is set to /var/tomcat4 Here is my simple jsp <%@ page language="java" %> <%@ page import = "java.util.*" %> <%@ page import = "java.io.*" %> <% Properties prop = System.getProperties(); %> Java class path: <%

Re: Classpath problems with Tomcat4 and RedHat 7.2

Do you have a CATALINA_HOME environment variable set? That might cause this... >>> [EMAIL PROTECTED] 05/07/02 09:21AM >>> I am having problems reading a resource file I placed in /var/tomcat4/common/lib. I also tried placing it in /var/tomcat4/common/classes. I wrote a small JSP which lists th

RE: Classpath problems with Tomcat 3.2

IT WORKED... Thanks... I didn't know that you have to expicitly import ALL classes... the import "*" blows up however... also of interest is that all of the Bean declarations have to have the -full- package name... Thanks again... JH > The problem is that your generated servlet code (

RE: Classpath problems with Tomcat 3.2

generated servlet Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net >-Original Message- >From: Jeffrey Hood [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 21, 2001 11:19 AM >To: [EMAIL PROTECTED] >Subject: RE

RE: Classpath problems with Tomcat 3.2

what is the URL you are using to access it? if it is http://dev.jhodd.com/subdir1/subdir2/test.jsp it should work right? Filip ~ Namaste - I bow to the divine in you ~ Filip Hanik Software Architect [EMAIL PROTECTED] www.filip.net >-Original Message- >From: Jeffrey Hood [mailto:[EMAIL P