Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
In-Reply-To: 
 <OF653454FD.E6868789-ON85257339.00661982-85257339.0066904B@mxi.com>
Subject: Re: Differences between JSP on-the-fly compilation and JSP
 precompilation
To: user@geronimo.apache.org
Message-ID: 
 <OFC50A38AE.1E65956F-ON85257339.00756250-85257339.0077F2F5@mxi.com>
From: Aman Nanner/MxI Technologies <aman.nanner@mxi.com>
Date: Thu, 16 Aug 2007 17:50:09 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII

This is an issue that relates to the G543818 Tomcat patch in Geronimo.
This patch seems to have implemented instance manager pooling for tags.
Geronimo requires this, and in order to enable this for precompilation, the
following Java system property needs to be set in the precompilation
process:

org.apache.jasper.Constants.USE_INSTANCE_MANAGER_FOR_TAGS=true

If this property is not set, then precompiled JSPs that contain tags will
not work with Geronimo.  If this is not documented somewhere already, it
probably should.


Aman Nanner/MxI Technologies <aman.nanner@mxi.com> wrote on 08-16-2007
02:40:15 PM:

>
> I've tried precompiling my JSPs for the first time using the
> org.apache.jasper.JspC class.  The precompiling works fine, except I get
a
> runtime error in the JSPs when I try to access my web application:
>
> -------
> java.lang.UnsupportedOperationException: separate instantiation and
> injection is not supported
>       at
> org.apache.geronimo.jasper.
> JasperServletContextCustomizer$JasperInstanceManager.
> newInstance(JasperServletContextCustomizer.java:84)
>       at jspservlet.common.security.login.default_jsp._jspService(Unknown
> Source)
> -------
>
> I do not get this error when I do not precompile my JSPs.  After a little
> investigation, it seems that my precompiled JSPs are compiled differently
> then when they are compiled at runtime by the server.  The different code
> that is created after compilation triggers the above error in the
> org.apache.geronimo.jasper.JasperServletContextCustomizer class.
>
> I'm trying to figure out why these JSPs would be compiled differently in
> these scenarios.  Anybody have any ideas?
>
> I'm using Geronimo 2.0.
>
> Thanks,
> Aman
>
>
__________________________________________________________________________________

> * This message is intended only for the use of the individual or
> entity to which it is addressed, and may contain information that is
> privileged, confidential and exempt from disclosure under applicable
> law. Unless you are the addressee (or authorized to receive for the
> addressee), you may not use, copy or disclose the message or any
> information contained in the message. If you have received this
> message in error, please advise the sender by reply e-mail , and
> delete the message, or call (collect) 001 613 747 4698. *
>

__________________________________________________________________________________
* This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *