aspose file tools*
The moose likes JSP and the fly likes Adding JSTL to an old app: is this a compilation problem? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » JSP
Bookmark "Adding JSTL to an old app: is this a compilation problem?" Watch "Adding JSTL to an old app: is this a compilation problem?" New topic
Author

Adding JSTL to an old app: is this a compilation problem?

Thomas Kennedy
Ranch Hand

Joined: Jan 20, 2008
Posts: 137
I am adding jstl and tag files to an app that has neither. I'm getting

Tag 'insert' can't insert page '/content/paResultsContent.jsp'. Check if it exists. For input string: "${fn:length(pacode.value)}"

That jsp it says it cannot insert is included in the response by a Tiles template tag. But the code mentioned in the error occurs in a tag file included by the jsp:



I am using the correct 1.1 taglib directive and the 1.1 jars. We are running WebSphere 6.1, Java 1.5.0_30, JSP 2.0 and Servlet 2.4. It works fine on my local RAD where the only difference I can see is that it's Java 1.5.0.

It does not invoke my error handler page. Is this a compilation problem? Where can I find more information on what is breaking? I can find nothing in the logs.
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18541
    
    8

It sounds to me like your JSTL and taglibs are mostly working, except for this one strange thing. Is that right?

Anyway in the absence of any concrete information about the problem, I would take this:



and replace it by what I think is equivalent but simpler and potentially less problematic:


Thomas Kennedy
Ranch Hand

Joined: Jan 20, 2008
Posts: 137
Yes it works fine on my local RAD 7.0.0.1 but the response page blows up in our model environment which is the same apart from running on unix.

The tag file is invoked by another file which has a similar c:out tag, so if it were going to blow up I suppose it would have done so there. So I think the error message I'm getting is a red herring.

I've checked the usual log files under /profiles/, SystemErr.log and so on. There's nothing related to the problem. Is there some other location I should be checking?
 
jQuery in Action, 2nd edition
 
subject: Adding JSTL to an old app: is this a compilation problem?