--- Begin Message ---
All these JSP's are already in production and only recently we started to think about 
JSP precompilation.
The modification of included file name will work but will involve a overhead in terms 
of QA. 
 
So,is there a switch or a new version of Jasper that works for such situations.
 
Thanks,
Mani
 

        -----Original Message----- 
        From: Tim Funk [mailto:[EMAIL PROTECTED] 
        Sent: Thu 17-Jul-03 05:37 PM 
        To: Tomcat Users List 
        Cc: 
        Subject: Re: JSP include - compilation problem
        
        

        Rename include.jsp to include.jspx
        
        That way you also have a nice naming standard for knowing that a file is an
        included jsp or not.
        
        -Tim
        
        Manikandan Balasubramanian wrote:
        > We use Jasper that came with tomcat-3.3.1 for precompiling JSP's. Many of 
our JSP's use the following syntax.
        > 
        > parent.jsp
        > ===========
        > <jsp:useBean id="jspContext" class="com.schwab.base.presentation.JspContext" 
scope="request" />
        > ;
        > ;
        > ;
        > 
        > <%@ include file="child.jsp" %>
        > 
        > ;;;;
        > -----------------------------------------------------------------------------
        > 
        > child.jsp
        > ===========
        > <!-- CALHelp.jsp -->
        > <%@ page 
import="com.schwab.domain.configuration.model.AnchorsConfigurationFile" %>
        > <%
        > AnchorsConfigurationFile anchorConfig = 
AnchorsConfigurationFile.getInstance(jspContext.getCustomLocale());
        > %>
        > ....
        > ;;;;
        > 
        > 
        > At runtime,"jspcontext" is resolved and everything works fine. But at 
compiletime , child.jsp gets compiled separately and it throws and error for these 
undeclared variables.
        > 
        > How do we solve this ?
        > 
        > Thanks,
        > Mani
        > 
        > 
        >
        > **************************Disclaimer************************************
        >
        > Information contained in this E-MAIL being proprietary to Wipro Limited is
        > 'privileged' and 'confidential' and intended for use only by the individual
        >  or entity to which it is addressed. You are notified that any use, copying
        > or dissemination of the information contained in the E-MAIL in any manner
        > whatsoever is strictly prohibited.
        >
        > ***************************************************************************
        
        
        ---------------------------------------------------------------------
        To unsubscribe, e-mail: [EMAIL PROTECTED]
        For additional commands, e-mail: [EMAIL PROTECTED]
        
        

<<winmail.dat>>


--- End Message ---
**************************Disclaimer************************************

Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' and 'confidential' and intended for use only by the individual
 or entity to which it is addressed. You are notified that any use, copying 
or dissemination of the information contained in the E-MAIL in any manner 
whatsoever is strictly prohibited.

***************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to