Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 62079 invoked from network); 13 Jul 2003 17:20:35 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 13 Jul 2003 17:20:35 -0000 Received: (qmail 28918 invoked by uid 97); 13 Jul 2003 17:23:06 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 28911 invoked from network); 13 Jul 2003 17:23:06 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 13 Jul 2003 17:23:06 -0000 Received: (qmail 61298 invoked by uid 500); 13 Jul 2003 17:20:28 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 61278 invoked from network); 13 Jul 2003 17:20:28 -0000 Received: from s205-206-61-99.ab.hsia.telus.net (HELO marvin.local) (205.206.61.99) by daedalus.apache.org with SMTP; 13 Jul 2003 17:20:28 -0000 Received: from localhost (localhost [127.0.0.1]) by marvin.local (8.12.8/8.12.8) with ESMTP id h6DHKKc3008410 for ; Sun, 13 Jul 2003 11:20:21 -0600 Subject: Re: JasperException From: Reginald Oake Reply-To: regoake@assistants.ca To: tomcat-dev@jakarta.apache.org Content-Type: text/plain Organization: Computer Assistants Message-Id: <1058116820.1521.34.camel@marvin.local> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 13 Jul 2003 11:20:20 -0600 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi. Just to let you know that it appears that I have this problem solved (at least I got a JSP to compile once). Thanks to Tim Funk for his help in this although the solution to the problem actually came from a different source. I have been running Jakarta 4.1.24 LE (for java 1.4.x) and recently updated my development machine (the one on which I was having this difficulty) to j2sdk1.4.2 which I got from java.sun.com. I thought I had also done the same to my production server but was mistaken. I copied the j2sdk (j2skd1.4.1 from blackdown.org) directory from my production server to my development machine, restarted Tomcat and now everything appears to be back to normal. I have no idea whether this indicates that there is a problem with Sun's j2sdk1.4.2 or with j2sdk on Linux only or if blackdown's j2sdk is simply better in this respect but it might be worthwhile to add this to the list of possible solutions to this problem. Again, thank you for your help with this situation. Reg --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org