Literals are acceptable for both MethodExpression and ValueExpression in both deferred and immediate invocation.
MethodExpression example: public String method() can just be 'cart', which will be returned as the result. In the converter case, a single attribute handles both the 'named' converter case and the 'pointer' converter case. When the ValueExpression is literal (ve.isLiteralText()) is called on the set ValueExpression, it instead defers the Converter lookup to the JSF application instance, and not as an invokable expression pointer to an instance in EL. >[EMAIL PROTECTED] wrote: >> It doesn't look like it's picking up the fact that the expression is >literal. >> >> Both pertinent classes look correct from Tomcat: >> >> >http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/org/apache/jasper/el/ >JspValueExpression.java >> >> >http://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk/java/org/apache/el/ValueEx >pressionImpl.java > >I did add the check in checkXmlAttributes that is failing, so maybe it's >my fault. Apparently, the attribute is a literal (not an expression) >with a value of "creditCardConverter" and I don't see how this can be >cast to an instance of javax.faces.convert.Converter. > >Can you attach the JSP fragment that is causing problems ? > >(Did I miss something ?) > >Rémy > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
