JSP/Expression Language in Web AS 6.40

Hello
We are trying to port a Servlet/JSP Application from Tomcat to SAP Web AS. It's based on Spring/Hibernate and we are heavily using JSP with Expression Language and JSTL.
The first problem i had with the "c:forEach" tag, was solved by using the "core" taglib instead of the "core_el" taglib (which means JSTL without Expression Language seems to work)
As i found out SAP Web AS 6.40 complies to the J2EE 1.3 Standard. Therefore it supports JSP 1.2 and not JSP 2.0 with Expression Language EL.
Despite not supporting the current JSP Standard, is there any possibility to get JSP Pages with Expression Language running on Web AS 6.40?
If no, is it planned to support JSP 2.0 in future versions of Web AS and when is it scheduled?
Thanks for answers
Sigmar

Sigmar,
there is already released light version of J2EE engine including J2EE1.4...You can have a look at the begin page of the SDN, or directly download it by link :
https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/webcontent/uuid/64919927-0b01-0010-e9bf-d1570518023d [original link is broken]
As bonus it includes Java EE 5 preview
Regards
Bojidar

Similar Messages

Help needed in JSP Expression Language

Hi all,
I have been working for JSP Expression Language Sample execution since past 5 days. I am using the application server as "Jboss Server" and web server as "Tomcat".
I have been included the jsp-api.jar file in my lib directory of application server as well as source folder's lib directory.
When i am trying to build the source code, i am getting this build error.
[javac] D:\eclipse\workspace\esolvProject\development\src\com\esolv\taglibs\
web\classes\SetSupport.java:186: cannot resolve symbol
[javac] symbol : method getExpressionEvaluator ()
[javac] location: class javax.servlet.jsp.PageContext
[javac] ExpressionEvaluator evaluator = pageContext.getExpressionEvaluator();
In my jsp-api.jar , there are two classes called,
PageContext and JspContext, Both are abstract classes.
PageContext inherits JspContext class. JspContext class have the method getExpressionEvaluator() , returns ExpressionEvaluator.
PageContextImpl - class . it has been called internally when we are trying to call PageContext class. In PageContextImpl class, there is one comment before, the method's definition. that is
" Since JSP 2.0 "
But we have the JSP 2.0 version. But it won't work.
Please help me ont this.
Thanks in Advance,
Natraj

>
If the pblm was due to setting the classpath.
The error should be showed for all files in the jar
file.
why i am getting the error for particular method ?
it is accessing the other methods of same class
'JspContext' . but it is not accessing that method.
Thats my question.
Just check that your .jar file is 2.0 compliant and that you do not have any other jars(for servlet or jsp api) in the classpath.
Probably you have an older version of .jar file in your path. So the errors will appear only for those methods that have been added since 2.0, all other methods would compile fine.
Please tell me the jar files to work out the
expression language. so that i can cross check my
list of jars.Hmmm...I dont use jboss. In tomcat the jar file name is jsp-api.jar. But it would have been the same even for jsp1.1, going by jar file names wouldnt help. Just look at your cp as if with a microscope to identify redundant jars.
cheers,
ram.

The JSP Expression Language

Developing and Using Functions
iam new to use the jsp ..
iam learning how to use taglib.
user defined functions
tell me steps to write user defined function using taglib
iam trying run the Code sample 3
in the given url..
http://java.sun.com/developer/technicalArticles/javaserverpages/JSP20/

Read this: http://java.sun.com/products/jsp/tutorial/TagLibrariesTOC.html
=======================================================
To use these tags, you need to have 4 files:
1. Your .java file with the function ( the add() method in your case )
2. A .tld file, the taglib descriptor, to hold the 'function descriptor' as you call it. This maps the tag to the Java method
3. The web.xml, it has to have entries that tell the container ( Tomcat? ) where to find the TLD for a particular URI (http://jakarta.apache.org/tomcat/jsp2-example-taglib in your case )
4. The JSP page with the taglib directive as you've already made.
=======================================================
How it works is:
1. the JSP page taglib directive tells the container that the prefix 'my' will refer to the taglib identified by the URI "http://jakarta.apache.org/tomcat/jsp2-example-taglib".
2. The container must now know which tag library is being referred to. The container, during startup, tracks all the entries in the web.xml and maps the URI with the location ( taglib-uri and taglib-location ).
3. The location points to your Java class: one.Compute
=======================================================
My doubt:
1)where i have to place the function descriptorThis is to be part of a .tld file, the taglib descriptor. Let's assume you save this TLD as myTaglib.tld and place it in /WEB-INF. Your entry will be like this:
<taglib xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
web-jsptaglibrary_2_0.xsd"
version="2.0">
<tlib-version>1.0</tlib-version>
<function>
        <description>add x and y</description>
        <name>add</name>
        <function-class>jsp2.examples.el.Compute
            </function-class>
        <function-signature>int
            add(java.lang.String,java.lang.String)
                </function-signature>
    </function>
</taglib>------------------------------------------------------------------------------------------------
2)<%@ taglib prefix="my"
ri="http://jakarta.apache.org/tomcat/jsp2-example-tagl
ib %>in the url just i have to mention that url else
anything i have to edit it.This is fine, as long as the URI value matches the taglib-uri element in your web.xml
You web.xml should have an entry :
<taglib>
<taglib-uri>
http://jakarta.apache.org/tomcat/jsp2-example-taglib
</taglib-uri>
<taglib-location>
/WEB-INF/myTaglib.tld
</taglib-location>
</taglib>
3)i had placed the compute .java program inside
package one is it necessary to place that program
in separate package else i can place it along other
java files.
) is i have to include any jar or TLD files in my
project ..All your loose classes ( .class files ) go into /WEB-INF/classes. They should be in folders representing the package heirarchy. So in your case, you've not declared the package in the code given. So I'm assuming you have
package one; in your .java file.
So your class should go into /WEB-INF/classes/one/Compute.class
All JARred classes ( in the form of .jar archives ) should be put into the /WEB-INF/lib folder.
The post is a bit messy but I think I've managed to get the basics right :)

JSP expression language

Hello,
When I edit .JSP file with JDeveloper 10.1.3.1, the tag is underlined with the yellow line
<jsp:include page="${param.content}" />. I am sure it's very easy to fix, does anyone know how?

Hi, Chris Muir:
The <jsp:include> tag documentation says the page attribute requires round brackets
around the value, as follows:
<jsp:include page="({$param.content})"/>That understanding is wrong. You are referring to the following documentation in JDev online help, right?
JSP syntax <jsp:include page="(relativeURL | <%= expression %> | ${ Expression })"
[flush="true | false"]
[jsp:param]>
</jsp:include> Here the round brackets "( )", together with the vertical lines "|" is just to indicate several choice are available. The page attribute does not require round brackets. If you do include round brackets, they will become part of the value for the page attribute, which is certainly not what one want. The same can be said about the square brackets around flush or jsp:param.
Alternatively a yellow/orange line in the JDev editor usually indicates a warning, not an
error. On the left hand side of the editor, is the code assist icon showing (a lightbulb),
and selecting it, does it reveal any useful info?
Alternatively (x 2) on the right hand side of the editor, is there a yellow box showing,
and hovering your mouse over the yellow box for a second or two, does any useful
information show?These are nice suggestions. Still another alternative. Hover your mouse right above the yellow line, a small message window pops up. It shows the relevant reason for the yellow line. That at least works for me.
Moreover, the warning is, "${param.content} is not found under root C:\jdev\studio10131\jdev\mywork\Application1\Project1\public_html\". It is just a warning. This warning is as much as JDev can do since ${param.content} is a runtime expression that can not be resolved at design time. One can safely ignore it as long as one remembers to create the alluded page.

How to check arraylist size greater than 1 using expression language in jsp

I want to remove the scripplet in jsp, so i am using jstl tags with expression language in it.
My scripplet is
<% if (arraylist.size() > 1) {
---do something ----
%>
i wanted to change this to
<c:if test="${ somecondition }">
---do something ----
</c:if>
here "somecondition" is exactly i need to check whether my arraylist size is greater than 1.
so please can anyone help me how can i do that.

If you do not mind, you can create a function and package it into a tag library of your own. Then you can use the function just as the existing expressions language construct. You may take a look at the article use functions in jsp expression language.

Unified Expression language framework in another context than JSP/JSF

Hi
+(I hope this is the right place for such question)+
We are building some RCP apps and we are in need, for our frameworks, of a expression language that allows to get and set values, and other things, and it seems that the Unified Expression Language Framework meets our need.
However, as I said, this is a RCP app, not a web app. So my question is
Is this framework designed to be used outside of the web app context (jsp, jsf, etc) ? Or is there any dependencies that would prevent or make it difficult to use it in a GUI RCP application?
Thanks for your help
cd

BalusC wrote:
It's so cool that you can change the way to read your sentence. I never read it any other way. I probably shouldn't have posted a double meaning statement but saying that I'm changing the way I read it is incorrect. I'm not doing that.
BalusC wrote:
It's also a great coincidence that you mention exactly the references which are implicitly available in the scriptlet world.Not sure what that's intended to mean. I was exposing to the OP the part of EL that deals with objects that require/assume a j2ee container.

JSP 2.0 Expression Language

Quick question on EL:
- I noticed in the J2EE 1.4 Tutorial that the Expression Language syntax can be used outside of any JSP tag, for example
${name.lastname}is valid, even if used anywhere in the page, i.e. outside of any tag.
Is this a new feature of JSP2.0, or is this possible using JSTL with prior versions of JSP?
Thanks, Kevin

JSP 2.0

Expression Language in JSP w/ JSTL

Does expression language decrease performance on the page?

I was browsing the forums and i came across
http://forum.java.sun.com/thread.jspa?threadID=349876&messageID=1450081
The only difference is that I'm using Tomcat 5.0...
Our pages are running slow and we can't figure out what's wrong...

{Expression Language} not working tomcat5 j2se 1.5_beta

I m new to JSP technology. I m trying to use expression language in my application and it's not letting me do the job.
simple program
<head> <body>
Hi there! 3 + 3 is ${3+3}
</body></head>
It just shows " Hi there! 3 + 3 is ${3+3} " as the output. I tried google search. it seems the problem is across many networks like in bea weblogic etc.,
when i used <%@page isELEnabled="true" > i get an error saying attribute isELEnabled not recognised or something like that. My web.xml hasn't got any setting for jsp so I don't know where the "*.jsp" section is available, just in case that needs any touchup.
I have installed JSTL under /common/lib dir. but i think this library is not required for using basic EL.
So, can anyone help me configure my JSP page so that i can use EL tags in them.
OS: Windows 2000
Tomcat ver: 5
J2Se: 1.5 beta

Hmmm. Looks like I didn't make myself clear enough.
You still have the declaration DTD for servlet 2.3 at the top of your web.xml.
To enable EL using Tomcat 5 you only need to do ONE of the following:
1 - update your web.xml file to have the header for the 2.4 version (note its not a DTD anymore)
2 - if your web.xml uses the DTD from version 2.3, include the page directive <%@ page isELIgnored="false" %> on any pages
Basically the rules for executing EL are as follows:
1 - Is there a directive on the page? If yes, then enable/disable according to the directive.
2 - Is there an entry in web.xml for handling EL? If yes then enable/disable according to the setting
3 - Is the web.xml file for the Servlet 2.4 spec? (ie does it start have the version 2.4 header) Yes = enable EL No = disable EL
The easiest way of enabling EL is updating your web.xml to be compliant with the latest servlet spec.
Cheers,
evnafets

Text/expression-language-based paradigma continues?

i've been working with jsp and struts for a while. the most significant drawback of jsp, custom tags/jstl and struts is its "runtime" binding caused by the heavy use of string-attributes and interpreted expressions.
it makes the coding itself harder (loss of compiler support and strong typing), it increases the amount of testing (automated tests, regression tests) extremely, it makes jsp-apps very hard to mantain, it is error-prone when changed or refactored, it is slower in execution and last but not james requires extra developement tools (such as struts-editors) to effectively maintain the applications.
but i like the paradigma of a web application that keeps a view state, handles "events" etc.
the only thing i can't understand is why jsf builds on the error-prone jsp/custom tag paradigma instead of compiled server side ui components. it obviuosly still tries to follow the myth, that web-designers and application developers can share their source (i.e. js-pages) by using tags. imo this is a degeneration of the good idea to leverage html by some custom tags. these tags empower designers to make their pages dynamic. (enterprise) software developement ist very different: complex use cases, business logic and often ui-"logic", integration issues etc...
the life cycle of a jsp with custom tags is weird (even more in struts):
- objects (variables in scriptlets) already existing in the scope of the jsp-execute-method are wrapped into attributes of page, request or application scope.
- tags are defined using string-based attributs, such as <html:write name="pinky" property="brain" />
- the implementation of the tag tries to look up the object in any of the scopes, starting with page scope
- if the object exists, it tries to read/set its property via reflection
so you lose strong typing, compile time checks and performance.
there are several frameworks that do not build upon jsp and tags but put in an extra layer. this layer is similar to a rich client "form" and renders the output into html or any other format.
so i'm not preferring any framework, just looking around and curious why this architecture has been chosen for jsf.
thanks
tom

the most significant drawback of jsp, custom tags/jstl and struts is its "runtime" binding
caused by the heavy use of string-attributes and interpreted expressions.I second this heartily.
but i like the paradigma of a web application that keeps a view state, handles "events" etc.
the only thing i can't understand is why jsf builds on the error-prone jsp/custom tag
paradigma instead of compiled server side ui components. The JSF - JSP connection is a major problem. More and more developers are starting to express reservations about it, because the two technologies don't play well together. But I think you've hit on an even deeper fundamental flaw in the equation -- the evils of runtime binding. The heavy JSF/JSP reliance on runtime evaluation is a reliability nightmare. Developers choose Java, in part, because of the robustness provided by compile-time checking. We give that up when it comes to JSF/JSP or Struts web applications, and that's an unacceptable state of affairs.
Winer says that "JSF has taken a major step in the right direction with the <managed-bean> and <referenced-bean> configuration elements. These give some hope for development tools to finally provide real code insight (and even error reporting) for EL expressions, because they define both what keys are used in the expression language and what types of objects may be at those keys." However, this will help with only the simplest EL expressions. As soon as an EL expression reaches into nested properties and maps that aren't defined in the config file, we're back to runtime binding and error reporting. The addition of generics to the language with 1.5 might have made it possible to introduce strong EL type checking at page compile time, but Sun's short-sighted type-erasure implementation of generics rules this out permanently.
Look at what Microsoft is doing with ASP.NET. It's not perfect, but the fundamental technology is based on compiled server side ui components. There are places in that framework where you can write expressions aren't evaluated until runtime, but it's certainly not the fundamental basis of the model as it is with JSF/JSP. And the .NET implementation of generics may make it possible to have these dynamic expressions type-checked at page compile time in a future implementation of .NET.
I keep reading comments from the JSF proponents who say things to the effect of "yes, we know JSP doesn't play well with JSF, but JSF allows you to plug in a different rendering technology." Well, we need one, and we need it urgently. ASP.NET has been out for two years now, and was far more polished and useable at its release than JSF is now after a very long development cycle.
Rightly or wrongly, people will judge JSF on the merits of the reference implementation. And I fear that a lot of developers are going to throw up their hands after a taste of the JSF/JSP world and move to .NET.
Stephen Schaub

Expression Language support in Weblogic portal workshop8.1 sp5

while i was developing the jsp pages in Weblogic portal workshop8.1 sp5, though i included jstl.jar and standard.jar in WEB-INF\lib , my jsps are not recognising expression language statements like ${initParam.name}? what might be the reason for this problem?
pls do the needful.

Weblogic 8 is J2EE1.3 compliant.
That means Servlet2.3 / JSP1.2
Which means it won't understand the EL on its own.
EL was added with JSP2.0.
You need to use JSTL1.0 with this server, and the EL expressions can only be used within the JSTL tags, or tags especially written to understand EL.

Enable Expression Language JSP2.0

how do you enable Expression language (eg. ${1 + 1}) in JSP pages using Tomcat5 alpha? The examples that come with Tomcat have it enabled, but when I create my own application context it isn't enabled.
Thanks for any help.
duke

I am having the same problem: I'm running Tomcat 5.0.4. All the shipped JSP and JSP2 samples work nicely. When I try the same, the EL expressions are not evaluated (the compiled JSP shows that it simply literally outputs any EL expression). I have compared the web.xml files but I cannot make it work. I suppose I am missing some switch to enable the evaluation of EL expressions.
Any help is greatly appreciated.
Heiko

About Expression Language

Is it necessary to use JSTL along with Expression Language..
I have added following tags in application's web-xml file.But without JSTL tags the output is not as expected..
Plz help me.
<jsp-config>
<jsp-property-group>
<url-pattern>*.jsp</url-pattern>
<el-enabled> true</el-enabled>
<scripting-enabled>true</scripting-enabled>
</jsp-property-group>
</jsp-config>

Yog82 wrote:
<el-enabled> true</el-enabled> <el-enabled> has been changed to <el-ignored> in the JSP 2.0 spec.
And you don't need the JSTL for using EL. Make sure you web.xml is specified to be version 2.4 and not 2.3. With 2.3, EL is disabled by default but is enabled by default in 2.4. So with 2.3, you need to use JSTL to use EL.
Read this:
http://forum.java.sun.com/thread.jspa?threadID=557423&messageID=2736439
http://forum.java.sun.com/thread.jspa?messageID=1643708&tstart=0

Expression Language not getting evaluated

I am trying a sample on tomcat 5.03. The expression Language construct is not getting evaluated.
for eg
<c:out value="${customer.age}" />
simply prints the text ${customer.age} .
Whats wrong ?
Thanks
Ashwani

You probably have an old doctype for your web.xml file.
Your web.xml needs to start like this:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" version="2.4">It should NOT have this
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">Basically if it sees anything less than version 2.4 in the web.xml file, it will disable EL expression language for your JSP pages. This is for backwards compatibility with existing web apps.
To fix - remove the doctype definition, and use the new one.
alternative: put this on your jsp page:
<%@ page isELIgnored="false" %>That will fix it for this page. Fixing the web.xml should fix it for all pages.
Cheers,
evnafets

BUG: Expression Language not supported (JDeveloper 10.1.3.0.4(SU1))

Hi!
I have the following code in a jspx page:
<c:if test="${!empty bean.genericErrorMessages}">
<h:outputText styleClass="texto_red"
value="#{bean.genericErrorMessages}"
id="applicationErrorMessages" escape="false"/>
</c:if>
All code compile well, but when i run the jspx page the following exception occur.
The problem is that in JDeveloper Early Access 3 the problem doesn't occur.
But in the Jdeveloper version 10.1.3.0.4(SU1) the exception occur.
I'm running JDeveloper in a Windows XP SP2, JSF 1.1_01 and JSTL 1.0
Does anyone know a solution to this problem? Tanks.
The Exception:
Error: Expression Language not supported in compile time attribute test
     at oracle.jsp.parse.JspUtils.hasELWithCreation(JspUtils.java:1248)
     at oracle.jsp.parse.JspUtils.processELAttribute(JspUtils.java:1274)
     at oracle.jsp.parse.OpenJspTagHandler.processAttributeValue(OpenJspTagHandler.java:331)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1368)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:739)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:739)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:739)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:739)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.OpenJspTagHandler.parseXMLSrcBody(OpenJspTagHandler.java:739)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTag.parse(JspParseTag.java:1413)
     at oracle.jsp.parse.OpenJspTagHandler.parse(OpenJspTagHandler.java:802)
     at oracle.jsp.parse.JspParseTag.genXMLSrcTag(JspParseTag.java:867)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcNextTag(JspParseTag.java:745)
     at oracle.jsp.parse.JspParseTag.parseXMLSrcBody(JspParseTag.java:1121)
     at oracle.jsp.parse.JspParseTag.parseXMLSrc(JspParseTag.java:1375)
     at oracle.jsp.parse.JspParseTagFile.parseXMLSrc(JspParseTagFile.java:296)
     at oracle.jsp.parse.JspParseTagFile.parse(JspParseTagFile.java:211)
     at oracle.jsp.parse.OracleJsp2Java.transform(OracleJsp2Java.java:403)
     at oracle.jsp.runtimev2.JspPageCompiler.attemptCompilePage(JspPageCompiler.java:558)
     at oracle.jsp.runtimev2.JspPageCompiler.compilePage(JspPageCompiler.java:348)
     at oracle.jsp.runtimev2.JspPageInfo.compileAndLoad(JspPageInfo.java:610)
     at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:634)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:370)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:478)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:401)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:719)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:298)
     at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:42)
     at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:205)
     at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:209)
     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     at org.apache.shale.faces.ShaleViewHandler.renderView(ShaleViewHandler.java:143)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:122)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at pt.ivv.commonbusiness.presentation.servlets.filter.HibernateFilter.doFilter(HibernateFilter.java:68)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:534)

Hello,
You should not try to mix JSP and JSF EL prior to JSF 1.2 and JSP 2.1, the result is inconsistent most of the time.
To fix your current issue though, I suggest you use the rendered attribute instead of a <c:if>, so would be:
<h:outputText styleClass="texto_red"
value="#{bean.genericErrorMessages}"
id="applicationErrorMessages" escape="false" rendered="#{!empty bean.genericErrorMessages}"/>Regards,
Simon Lessard

JSP/Expression Language in Web AS 6.40

Similar Messages

Maybe you are looking for