ognl classresolver

[Norbert Sándor <de...@erinors.com>]

Hi,

I wanted to submit a feature request but before I do so I ask you whether it is a bad usage-pattern or not.

In one of my previous projects I used OGNL for expression evaluation. Because OGNL expects fully qualified class names, I've created a custom classresolver which first checked a static list of classname-abbreviations (coming from a .properties file) like

List=java.util.List
Map=java.util.Map
...
MyClass=my.long.package.name.MyClass

I'm thinking about implementing the same in Tapestry 4. I want to create a custom ExpressionEvaluator which uses a Hivemind configuration point to define the abbrevations. (Sad but the current implementation does not support subclassing - which is a weak point in core classes I think. There were several issues about "making XY subclassing-friendly". For example in case of ExpressionEvaluatorImpl it stores the ClassResolver in a private member which cannot be changed from "outside".)

Of course, only in-house component libraries or own applications should use this method.

What do you think, would this lead to problems?
Does anyone else find this a good feature?

BR,
Norbi