[
https://issues.jboss.org/browse/AS7-3332?page=com.atlassian.jira.plugin.s...
]
Stan Silvert commented on AS7-3332:
-----------------------------------
That part of the spec just means that you can use the Facelets versions of some JSTL tags.
It does not mean that you can use the actual JSTL tag library. Since I saw your declared
namespace
xmlns:c="http://java.sun.com/jsp/jstl/core", that's what I thought
you were doing. I didn't remember that JSF 2.1 supports both
http://java.sun.com/jstl/core and
http://java.sun.com/jsp/jstl/core. Sorry for my error.
Anyway, the Facelets version of the tag is completely different code, so it's not
surprising that they work (or fail) differently.
I'm thinking the problem may be in your <c:if> tag rather than the
,<c:catch> tag. Have you tried replacing the $ with a #?
<c:if test="#{ex != null}">
c:catch tag apparently doesn't work when using facelets.
--------------------------------------------------------
Key: AS7-3332
URL:
https://issues.jboss.org/browse/AS7-3332
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.0.2.Final
Environment: JBoss application server running on a Windows 7 platform, inside
eclipse platform.
Reporter: Alexander Picoli
Assignee: Stan Silvert
Labels: c:catch, catch, facelets, jsf, jstl
Attachments: Boom.java, ccatchdemo.xhtml
When using the JSTL c:catch tag inside JSP pages, and I access an EL expression that
throws a custom exception, the tag works fine.
But when I use it with facelets, the c:catch is ignored and a HTTP500 message is sent to
the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira