[ 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. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-1353?page=all ] Gavin King updated JBSEAM-1353: ------------------------------- Fix Version/s: 1.3.0.ALPHA Priority: Blocker (was: Major) -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-1353?page=all ] Mike Quilleash reopened JBSEAM-1353: ------------------------------------ Just tried the latest CVS and still getting the same problem. I've traced it to this line in SeamApplication. @Override public ExpressionFactory getExpressionFactory() { //JBoss EL return SeamExpressionFactory.INSTANCE; } which is always returning the Jboss EL factory and not wrapping the expression factory of the wrapped application. I believe this should be changed to @Override public ExpressionFactory getExpressionFactory() { return new SeamExpressionFactory( application.getExpressionFactory() ); } -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-1353?page=comments#action_12364563 ] Gavin King commented on JBSEAM-1353: ------------------------------------ What I don't understand is how you are creating a "custom expresionfactory". AFAIK, there is no published API to do this. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-1353?page=comments#action_12364570 ] Mike Quilleash commented on JBSEAM-1353: ---------------------------------------- I have a custom ApplicationFactory that uses the standard chaining mechanism (single arg constructor of ApplicationFactory) and then an Application class like this... public class ApplicationImpl extends ApplicationWrapper { public ApplicationImpl( Application other ) { super( other ); } @Override public ExpressionFactory getExpressionFactory() { ExpressionFactory expressionFactory = super.getExpressionFactory(); return new ExpressionFactoryImpl( expressionFactory ); } } ApplicationWrapper just delegates all calls down to the "other" Application. I followed a similar pattern for the ExpressionFactory. The ExpressionFactoryImpl delegates most functionality down to the passed in "expressionFactory" but it does some checks and creates custom ValueExpressions for a couple of cases. You're probably right, I've never come across a spec for nesting ExpressionFactories like this. You can get the JSF RI 1.2 to use an el of your choosing by putting this in web.xml <!-- define the EL library to use --> <context-param> <param-name>com.sun.faces.expressionFactory</param-name> <param-value>org.apache.el.ExpressionFactoryImpl</param-value> </context-param> Although of course that is more configuration that has to be done. If I could change the application nesting so it was this... My Application -> Seam Application -> Default JSF Application then it would be fine, my application would get first look in when getExpressionFactory() is called. But at the moment the nesting is like this Seam Application -> My Application -> Default JSF Application so the call to getExpressionFactory() never gets delegated to My Application so it can add the custom expression factory. Hope that explains my issue. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-1353?page=all ] Gavin King closed JBSEAM-1353. ------------------------------ Resolution: Won't Fix Closing this, since a workaround exists, and this is not welldefined JSF functionality. -- 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