[ 
https://issues.apache.org/jira/browse/TAPESTRY-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jesse Kuhnert resolved TAPESTRY-962.
------------------------------------

    Resolution: Later
      Assignee: Jesse Kuhnert

Not an invalid issue - I do actually plan on making these kinds of changes but 
want to wait until ognl 3.0 comes out for that. (3.0 will involve a lot of 
things to make it easier to expose all of the core functionality in IoC 
containers. )

> enhance ExpressionEvaluator
> ---------------------------
>
>                 Key: TAPESTRY-962
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-962
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 4.0.2
>            Reporter: Norbert Sándor
>         Assigned To: Jesse Kuhnert
>             Fix For: 4.1.2
>
>
> ExpressionEvaluator abstracts OGNL by providing an OGNL independent interface 
> for evaluating expressions. It is very useful not only for bindings but for 
> custom usage as well. I'd like to propose some enhancements to make it more 
> useable:
> - add more configuration options, for example allow specifying a custom OGNL 
> class resolver
> - allow custom context variables like
>        public Object read(Object target, String expression, Map<String, ?> 
> variables);
>        The values in "variables" would be accessible as OGNL global 
> variables, eg. #mycustomvariable
>        For more information see 
> http://www.ognl.org/2.6.9/Documentation/html/LanguageGuide/varref.html
> (- maybe the interface should be renamed to OgnlExpressionEvaluator)
> (- maybe there could be configurable default variables when evaluating 
> bindings, like #locale -> requestCycle.engine.locale. These would help for 
> application developers to simplify the page files. I know that it is another 
> way to implement existing functionality - <inject> - but maybe it would be 
> useful.)
> The two latter are only quick ideas but the rest would be very useful!
> If you think so then I send my own ExpressionEvaluator implementation (which 
> is compatible with the current one in Tapestry).
> Regards,
> Norbi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to