Hello,
Most probably you're referring to this issue:
https://issues.apache.org/jira/browse/MYFACES-1670, aren't you? I've
tested Raphael's JSP locally and it's really the same problem. "mvn
-Dmyfaces.version=1.2.0 jetty:run" reproduces the error whereas "mvn
-Dmyfaces.version=1.2.1-SNAPSHOT jetty:run" doesn't. If Raphael doesn't
want to switch to MyFaces 1.2.1-SNAPSHOT, why not patching MyFaces locally?
regards,
Bernhard
P.S: I would have attached my sample application, but the spam
protection doesn't "like" it ..
Bruno Aranda wrote:
Hi, does it work if you use #{...} instead of ${...}? I seem to recall
a bug in myfaces 1.2.0 that has been fixed recently and it should be
fixed in the current snaphots (try myfaces-1.2.1-SNAPSHOT)...
Cheers,
Bruno
On 29/08/2007, Raphael Parree <[EMAIL PROTECTED]> wrote:
Hi,
This problem might have been addressed already within the mailing list. I
went trough the archives but was unable to find anything (now is the search
string "EL problem" not the best search string)
I'm in the process of upgrading to Tomcat 6 (6.0.14) and MyFaces 1.2.0. I
have a major problem with the EL. My JSF pages are using EL but know they
all resolve to empty strings (all EL on JSF pages, on JSPs they work).
For example the following fails:
<%@ taglib uri="http://java.sun.com/jsf/core " prefix="f" %>
<%@ taglib uri="http://java.sun.com/jsf/html " prefix="h" %>
<html>
<head>
<link rel="stylesheet" href="../../stylesheets/main.css"
type="text/css"/>
</head>
<html>
...
<p>Test:${pageContext.request.contextPath}, ${param.foo} </p>
<f:view>
<p>Test:${pageContext.request.contextPath}, ${param.foo} </p>
...
</html>
On both locations the result of the EL is empty.
Is this a known bug, does it have to do with libraries that i have available
in the lib?
Any help is welcome,
Kind regards,
Raphael
