Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 81472 invoked from network); 3 Aug 2000 03:58:24 -0000 Received: from mail.singingfish.com (@216.254.3.225) by locus.apache.org with SMTP; 3 Aug 2000 03:58:24 -0000 Received: (qmail 1003 invoked from network); 3 Aug 2000 03:56:39 -0000 Received: from c363190-b.sttln1.wa.home.com (HELO C363190B) (24.12.240.92) by mail.singingfish.com with SMTP; 3 Aug 2000 03:56:39 -0000 Message-ID: <020e01bffdc8$304db9f0$5cf00c18@C363190B> From: "Jonathan Reichhold" To: References: <200008030347.LAA12663@emu.os2.ami.com.au> Subject: Re: Using Class.forName() with Tomcat Date: Thu, 3 Aug 2000 20:58:00 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Actually you write the following code: try{ //The code in question } catch (Exception e) { System.err.println("Exception: " + e.toString()); e.printStrackTrace(); } To really see the exception and the details. I left out the details of the stack trace because I was asking if there is some sort of permisions issue with Class.forName() and Tomcat. I will not send the stack trace until I clean parts of it out. Jonathan ----- Original Message ----- From: "John Summerfield" To: Sent: Wednesday, August 02, 2000 8:47 PM Subject: Re: Using Class.forName() with Tomcat > > This is a multi-part message in MIME format. > > > > ------=_NextPart_000_01D6_01BFFD8A.A3899440 > > Content-Type: text/plain; > > charset="iso-8859-1" > > Content-Transfer-Encoding: quoted-printable > > > > I'm trying to load a class by name. The class is located in = > > $TOMCAT_HOME/webapps/ROOT/WEB-INF/classes and I am getting long stack = > > trace. Any reason why class for name won't work off of the ROOT = > > context? Is it a permission issue? > > > > > Sheesh. > > What do you think the trace is for, if not to tell you what went wrong? > > What do you think > try { > } catch (Exception E) { > } > is for, if not to report in a format YOU can understand. > > > > > Please, use the information and tools YOU have at hand, before wasting the > time and bandwidth of others. > > > >