You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Richard Mixon (qwest)" <rn...@custco.biz> on 2004/02/25 08:03:55 UTC
Tomcat 5 deployer compile errors on "<%@ include"s
I am trying to use the client deployer. Our JSP pages use a number of compile time includes such as "<%@ include
file="someCommonCode1.jsp" %>".
The client deployer is trying to compile each of these included files independently. I am getting compile errors all over the place.
The reason is that one include will imports a profiling package that some of the other includes depend upon.
The deployer is trying to compile each ".jsp" file as a complete page.
Is there another approach for handling compile time includes that will avoid this problem?
Is there a way to designate jsp files that should not be compiled independently?
Thanks in advance - Richard
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Tomcat 5 deployer compile errors on "<%@ include"s
Posted by "Richard Mixon (qwest)" <rn...@custco.biz>.
Tim,
Thanks. I went to the JSP 2.0 spec and they recommend using ".jspf". Here's what they say ( for any that might beinterested ):
--- SNIP BEGIN ---
( What Is a JSP Page 1-7 JavaServer Pages 2.0 Specification)
By default the extension .jsp means a top-level JSP file. We recommend, but do not mandate, to differentiate between top-level JSP
files (invoked directly by the client or dynamically included by another page or servlet) and statically included segments so that:
. The .jsp extension is used only for files corresponding to top level JSP files, forming a JSP page when processed.
. Statically included segments use any other extension. As included segments were called 'JSP fragments' in past versions of this
specification, the extension .jspf was offered as a suggestion. This extension is still suggested for consistency reasons, despite
that they are now called 'jsp segments'.
--- SNIP END ---
Thanks again for pointing me in the right direction.
- Richard
-----Original Message-----
From: Tim Funk [mailto:funkman@joedog.org]
Sent: Wednesday, February 25, 2004 5:22 AM
To: Tomcat Users List
Subject: Re: Tomcat 5 deployer compile errors on "<%@ include"s
The best thing to do is to not make compile time includes end in '.jsp'. Some
use .inc, other .jspi, and the spec might even have arecommendation for
compile time includes.
Also by using a specific file extension you can quickly identify its purpose.
-Tim
Richard Mixon (qwest) wrote:
> I am trying to use the client deployer. Our JSP pages use a number of compile time includes such as "<%@ include
> file="someCommonCode1.jsp" %>".
>
> The client deployer is trying to compile each of these included files independently. I am getting compile errors all over the
place.
>
> The reason is that one include will imports a profiling package that some of the other includes depend upon.
>
> The deployer is trying to compile each ".jsp" file as a complete page.
>
> Is there another approach for handling compile time includes that will avoid this problem?
>
> Is there a way to designate jsp files that should not be compiled independently?
>
> Thanks in advance - Richard
>
---------------------------------------------------------------------
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
Re: Tomcat 5 deployer compile errors on "<%@ include"s
Posted by Tim Funk <fu...@joedog.org>.
The best thing to do is to not make compile time includes end in '.jsp'. Some
use .inc, other .jspi, and the spec might even have arecommendation for
compile time includes.
Also by using a specific file extension you can quickly identify its purpose.
-Tim
Richard Mixon (qwest) wrote:
> I am trying to use the client deployer. Our JSP pages use a number of compile time includes such as "<%@ include
> file="someCommonCode1.jsp" %>".
>
> The client deployer is trying to compile each of these included files independently. I am getting compile errors all over the place.
>
> The reason is that one include will imports a profiling package that some of the other includes depend upon.
>
> The deployer is trying to compile each ".jsp" file as a complete page.
>
> Is there another approach for handling compile time includes that will avoid this problem?
>
> Is there a way to designate jsp files that should not be compiled independently?
>
> Thanks in advance - Richard
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org