This isn't a SSI include. It is a jsp include native to the jsp
specification? I did enable SSI just for kicks, but it doesn't change
anything.
Anyone?? I am really frustrated. What do I need to do to get rid of
the Illegal State Exception on a jsp:include?
I include on the first line,
Like in a previous reply to this post - we need more information (like a
code snippet) in order to provide a better answer.
You allude to Illegal State Exception. This can happen if you try any
of the following:
- Attempt to set headers (like cookies) inside of a jsp:include
- Attempt a JSP
:
09/17/02 10:28 AMSubject: Re: JSP Include error
Please respond to
Tomcat Users
Ok here is more info. These pages all work on tomcat 3 right now. I
have stripped down the page to the bare problem and still get the error.
I downgraded to Tomcat 4.0.4 because 4.1.10 has a problem doing regular
static include across a symbolic link. But for this problem of dynamic
I can reproduce this - strange. Can you try either of the following:
%String largeAd=/includes/468x60ad.txt;%
jsp:include page=%=largeAd% flush=true/
OR
The second one works, however it does write a warning to the logs that
the JSPNote javac.main has been depracated. Do you know why that is?
So I would say that something is wrong with jsp:include. However I
really don't want to rewrite every jsp:include across all of my jsp
pages!!
Any idea
Furthermore, I can't just read in the file, because in the real life
situation, it will have jsp code that needs to be executed in it.
-E
On Tue, 2002-09-17 at 11:01, Erick Todd wrote:
The second one works, however it does write a warning to the logs that
the JSPNote javac.main has been
I'm not sure about the compile warning.
I think it has to do with mime types needing to be decalred in web.xml.
For example: I have the following pages:
foo.jsp with the contents
hello jsp:include flush='false'
Great!! That was it. There should probably be some documentation about
that!?!?
I could not thank you enough!!
Erick
On Tue, 2002-09-17 at 11:11, Tim Funk wrote:
I'm not sure about the compile warning.
I think it has to do with mime types needing to be decalred in web.xml.
For
