#111 Validate OGNL expresssions against Java code

[Michael Echerer]

Hi,

it would be great if Spindle could automatically show a
warning in the problems dialog, if an OGNL expression
in a page or component spec doesn't match to the Java
code behind.

Example: You have a Home.java with some properties or a
listener method and you reference this in your page or
html with ognl.
Nothing prevents that you reference a non-existing
class, method or property in your Tapestry components.
Of course, you'll get a runtime exception later that
listener xyz was not found etc., but it would be great
to see it while editing.

That's especially true, because during refactoring of
Java code far far behind the scenes you might not
consider that some methods or properties are displayed
by any of your components and unfortunately it's not so
easy to get Eclipse consider OGNL expressions when you
refactor Java code... With some Spindle magic one could
at least see all open issues at once without having to
scan dozends of .html and .page files or by clicking
thru you application (or at best using web unit tests...)

[Geoffrey Longman]

Logged In: YES
user_id=387057

Since the tree of objects accessed by OGNL is only truely
available at runtime, it is hard to come up with a scheme to
do this reliably.

This has been raised many times before.

There are no plans to implement this behaviour.

If somebody thinks they can do it I can add an extension
point for a new plugin to validate OGNL expressions in this
manner.