RE: JSP Compilation Problem: Tomcat 4.1.12

Never mind. I found this described in Bug #10036. -Original Message- From: Sexton, George [mailto:[EMAIL PROTECTED]] Sent: 02 October, 2002 9:03 AM To: Tomcat Developers List Subject: RE: JSP Compilation Problem: Tomcat 4.1.12 I'm confused by the change in behavior. I can use JDK

RE: JSP Compilation Problem: Tomcat 4.1.12

I'm confused by the change in behavior. I can use JDK 1.4 w/ Tomcat 4.0.4 and it works. -Original Message- From: peter lin [mailto:[EMAIL PROTECTED]] Sent: 02 October, 2002 8:56 AM To: Tomcat Developers List Subject: Re: JSP Compilation Problem: Tomcat 4.1.12 if you're usi

Re: JSP Compilation Problem: Tomcat 4.1.12

if you're using jdk 1.4, you have to have package names for your classes. If you do not, it won't load the class correctly. have you tried giving your classes a package name and trying it again? peter "Sexton, George" wrote: > > I posted this several days ago on tomcat-user and haven't gotten

RE: JSP Compilation Issues (Multiple Domains)

+1 to the sync option > -Original Message- > From: Glenn Nielsen [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 01, 2002 9:45 AM > To: Tomcat Developers List > Subject: Re: JSP Compilation Issues (Multiple Domains) > > > Another way to fix this would be

Re: JSP Compilation Issues (Multiple Domains)

sage- >>From: Kin-Man Chung [mailto:[EMAIL PROTECTED]] >>Sent: Monday, September 30, 2002 9:47 PM >>To: [EMAIL PROTECTED] >>Subject: Re: JSP Compilation Issues (Multiple Domains) >> >> >>If you are using JDK javac for compiling the servlet >>ge

RE: JSP Compilation Issues (Multiple Domains)

; To: [EMAIL PROTECTED] > Subject: Re: JSP Compilation Issues (Multiple Domains) > > > If you are using JDK javac for compiling the servlet > generated by the JSP compiler, then you probably ran into the > problem that the javac not being thread-safe. > > In Tomcat 5 the j

Re: JSP Compilation Issues (Multiple Domains)

If you are using JDK javac for compiling the servlet generated by the JSP compiler, then you probably ran into the problem that the javac not being thread-safe. In Tomcat 5 the javac compilation is synchronized, so that the compilation is serialized. Guess that fix is not ported to 4.1.5. :-(

RE: Jsp compilation of nested custom tags (porting from weblogic 6 to tomcat 4.0.3)

window? Did you see me on the browser window as well? -Original Message- From: Kin-Man Chung [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:40 PM To: [EMAIL PROTECTED] Subject: Re: Jsp compilation of nested custom tags (porting from weblogic 6 to tomcat 4.0.3) I as

Re: Jsp compilation of nested custom tags (porting from weblogic 6 totomcat 4.0.3)

be verified. Thanks. > Date: Thu, 06 Jun 2002 18:54:11 -0400 > From: Pete Gordon <[EMAIL PROTECTED]> > Subject: Re: Jsp compilation of nested custom tags (porting from weblogic 6 to tomcat 4.0.3) > To: Tag Libraries Developers List <[EMAIL PROTECTED]> > Cc: [EMAIL PRO

Re: Jsp compilation of nested custom tags (porting from weblogic 6 to tomcat 4.0.3)

Thanks, Shawn. Let me summarize for the tomcat-dev list. I have an existing application with custom tags that runs on weblogic 6, when porting it over to Tomcat I now am running into an error where the generated java from a jsp with self nested tags will not compile, the code generated from jspc

Re: JSP Compilation

on 4/12/01 1:25 PM, "Glenn Nielsen" <[EMAIL PROTECTED]> wrote: > Are you feeling ok jon? > Your resounding "YES!" above could be interpreted as support for JSP. ;-) Yea, I just feel bad for all the poor lusers out there that have to use JSP because Sun or someone else pushed it down their CTO's

Re: JSP Compilation

Jon Stevens wrote: > > on 4/12/01 12:01 PM, "Glenn Nielsen" <[EMAIL PROTECTED]> wrote: > > > Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer > > uses the .java/.class versioning system because it uses a URLClassLoader for > > each JSP page compiled into a servlet. Tha

Re: JSP Compilation

On Thu, 12 Apr 2001, Glenn Nielsen wrote: > Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer > uses the .java/.class versioning system because it uses a URLClassLoader for > each JSP page compiled into a servlet. That way if the page is recompiled > the URLClassLoader f

Re: JSP Compilation

on 4/12/01 12:01 PM, "Glenn Nielsen" <[EMAIL PROTECTED]> wrote: > Reloading is not an issue in the Tomcat 4 version of Jasper. It no longer > uses the .java/.class versioning system because it uses a URLClassLoader for > each JSP page compiled into a servlet. That way if the page is recompiled

Re: JSP Compilation

[EMAIL PROTECTED] wrote: > > On Thu, 12 Apr 2001, Luise Massimo wrote: > > > Hi all, > > i have a simple question for which i haven't found an answare by myself: why > > for the same JSP page tomcat generate a new java/class file in work dir for > > every modification ? > > Reloading issues. >

Re: JSP Compilation

On Thu, 12 Apr 2001, Luise Massimo wrote: > Hi all, > i have a simple question for which i haven't found an answare by myself: why > for the same JSP page tomcat generate a new java/class file in work dir for > every modification ? Reloading issues. "Normal" reloading ( that is used for regula

Re: JSP Compilation

on 4/12/01 3:46 AM, "Luise Massimo" wrote: > Hi all, > i have a simple question for which i haven't found an answare by myself: why > for the same JSP page tomcat generate a new java/class file in work dir for > every modification ?