[
http://jira.jboss.com/jira/browse/JBSEAM-1353?page=comments#action_12363254 ]
Mike Quilleash commented on JBSEAM-1353:
----------------------------------------
Perhaps this custom ExpressionFactory would be better being created by SeamApplication.
It would remove the need for the SeamFaceletViewHandler as you could just check if
getViewHandler() returned a FaceletViewHandler.
SeamExpressionFactory breaks custom ExpressionFactories
-------------------------------------------------------
Key: JBSEAM-1353
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1353
Project: JBoss Seam
Issue Type: Bug
Components: EL
Affects Versions: 1.3.0.ALPHA
Environment: Any
Reporter: Mike Quilleash
Attachments: expressionfactory.patch
Trying out the current CVS and the modifications to the SeamExpressionFactory have broken
my application. In the old version SeamExpressionFactory used to wrap the
ExpressionFactory facelets would've created by default
(getApplication().getExpressionFactory()) but now it just wraps a jboss EL
ExpressionFactory.
I have a custom ExpressionFactory which i need to create custom ValueExpressions in
certain circumstances. The above change circumvents my ExpressionFactory when facelets is
compiling.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira