tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Burman" <richard.bur...@ardentia.co.uk>
Subject RE: Pre-compiled JSPs?
Date Wed, 07 Sep 2005 08:12:14 GMT
Hi Tim,

Sorry, I'm sure I'm being a bit dense but I seem to be missing something
important here.

Are the jspf files included (embedded) into the class file when Jasper
compiles the jsp files to java? Essentially, the compiled class file
will include the original jsp and also the fragment?

Thanks for your help!

Richard.

-----Original Message-----
From: Tim Funk [mailto:funkman@joedog.org] 
Sent: 06 September 2005 17:01
To: Tomcat Users List
Subject: Re: Pre-compiled JSPs?

There is no need to turn jspf into classes. The jspf are included by
real jsp 
files. Those jsp files are turned into the class files.

-Tim

Richard Burman wrote:

> Tim,
> 
> Is there no way of turning the fragment (jspf) file into .class files
or
> do they need to remain as JSPs?
> 
> Cheers,
> Richard.
> 
> -----Original Message-----
> From: Tim Funk [mailto:funkman@joedog.org] 
> Sent: 06 September 2005 16:14
> To: Tomcat Users List
> Subject: Re: Pre-compiled JSPs?
> 
>  From the jasper task all the [valid] jsp's are turned into java files
> and 
> compiled into class files. Those class files need to be a jar file in 
> WEB-INF/lib or inside WEB-INF/classes. The jasper task can also
rewrite 
> web.xml so that all the mappings from the JSP --> class file are taken
> care of.
> 
> Once all the jsp's are compiled and mapped in web.xml. They can be
> deleted 
> from the deployment war file (or dir).
> 
> 
> -Tim
> 
> Richard Burman wrote:
> 
> 
>>Hi Tim,
>>
>>Yeah, that's my exact issue, except the pages somewhat more
> 
> complicated
> 
>>than your example. ;o)
>>
>>I've tried renaming one of them to jspf and, unsurprisingly, it has
> 
> been
> 
>>ignored by the JSP compiler. I'll have to take your word that it would
>>still work in the parent (once the reference had been changed to point
>>to jspf, not jsp) as I don't have a test bed up and running at the
>>moment.
>>
>>Okay, so we've ascertained how to avoid the 'fragments' being compiled
>>because they're effectively not valid JSP pages because they use beans
>>that are never declared within themselves. The 'parent' page will
>>compile because it has all it needs to be compiled but the fragment
>>cannot be compiled without the presence of the parent. Does this mean
>>that I can only include the 'parent' JSPs in my JAR file and included
> 
> in
> 
>>my web.xml? Do I have to keep the fragments as raw JSPs in my webapp,
>>then? I'd really rather get them all together in a JAR, if possible,
>>which is why I'm on this voyage of discovery! :o)
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message