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]>
> Subject: Re: jasper package
>
> > 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 want this because I need it to debug my
> generated class file at runtime. Currently, jasper
> will always generate class in org.apache.jsp. For
> example, /abc/test.jsp will have class in
> $scratchDir/abc, and /abc/def/test.jsp will be
> generated in $scratchDir/abc/def, with the same
> package - org.apache.jsp! I can not even compile these
> classes, do you think it a good design?
>
> Or, what I need is compile and debug, I do not need
> that flexibility to specify package name, at least, I
> think jasper should support this: these jsps will have
> package name org.apache.jsp.abc and
> org.apache.jsp.abc.def respectively.
>
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.
>
> Yunfeng Hou
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>