BEA 9.2, JSTL Exploded EAR problem

Question

Application is originally deployed as EAR.
To allow faster development I have installed it as exploded view. Within BEA I have removed EAR deployment (which is working fine), and set up EXPLODED ear. Setup is exactly the same, with exception of selecting EAR folder.
However, for me it does not work. I got number of errors similar to:
frontendLayout.jsp:20:35: This attribute does not support request time values.
<c:set var="displayedObjectTitle" value="${requestScope[pageScope.DISPLAYED_OBJECT_TITLE_KEY]}" />
with:
compile.jsp=true
I can not even "Accept Changes" (on BEA Web console).
With:
compile.jsp=false
I can accept changes, but each page I open shows number of errors similar to one above.
Did someone have similar issue and was is resolved?
One of possible solutions for issue could be (as I found it somewhere) replacement of:
<%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
with:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
But there too many pages to change, that I did not even tried it.
Does someone know what is causing this issue? How can I Resolve it? It obviously has something to do with JSTL versions, but what is the best way to resolve it?
Thanks.

Answer 1

One of possible solutions for issue could be (as I found it somewhere) replacement of:
<%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %>
with:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
Just read this. That's correct.
But there too many pages to change, that I did not even tried it. Why do you have that embedded in each page? A better solution would be to write an include.jsp and then just @include that. One change and all the pages see it.
Does someone know what is causing this issue? How can I Resolve it? It obviously has something to do with JSTL versions, but what is the best way to resolve it?See above.
%