> The Java compiler used by Tomcat doesn't have any
> problems compiling the
> sources that are currently being generated. What
> compiler are you trying
> to use that has problems with it? That's where your
> problem really
> appears to lie.
>
Yes, because the magic class loader has the trick
> The compiler driver and classloader used by tomcat
> does a lot of magic to
> get it to work. All jsp files named, for example,
Yes I know the class loader has the job done, is it
bearking the convention? Anyway, I can debug my jsp
now with the jasper I patched.
Yunfeng Hou
__
ntly, then go ahead and ignore all this. I
know this applied for 4.0.3.
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 20, 2002 1:28 AM
> To: Tomcat Developers List
> Subject: Re: jasper package
>
>
>
>
> O
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 19, 2002 6:11 PM
> To: Tomcat Developers List
> Subject: Re: jasper package
>
>
>
>
> On Mon, 19 Aug 2002, [gb2312] Yunfeng Hou wrote:
>
> > Date: Mon,
On Tue, 20 Aug 2002, [gb2312] Yunfeng Hou wrote:
> Date: Tue, 20 Aug 2002 13:13:14 +0800 (CST)
> From: "[gb2312] Yunfeng Hou" <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: Tomcat Developers List <[EMAIL PROTECTED]>
>
> A desire to do this in the first place probably
> comes from wanting to use
> unpackaged classes without importing them -- which
> is both against the JSP
> spec and is also frowned on in general by the Java
> compiler in JDK 1.4 and
> later. You're MUCH better off putting your classes
No, I w
On Mon, 19 Aug 2002, [gb2312] Yunfeng Hou wrote:
> Date: Mon, 19 Aug 2002 11:35:17 +0800 (CST)
> From: "[gb2312] Yunfeng Hou" <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: jasper package
>
> Jasper has command line option to set pa
