Hi James,
thanks once again for your answer! ;)
| Your components can parse OGNL automatically by preceding your expression
| with "ognl:" in the attribute value. However, you do have to stick with the
| OGNL specification and can't just make up your own formats on the fly. If
| you want to use
n your sub-expressions and it'd
use the appropriate translator to parse the value based on the prefix.
Maybe you should suggest that to one of the HiveMind team! :-)
-Original Message-
From: Andreas Bulling [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 19, 2006 1:27 PM
To: Tapestry
Hi all,
concerning the AdminPanel component mentioned in one of my
earlier posts I have another problem:
As some of the possible object properties need some kind
of conversion before getting displayed in the panel
(the date for example) I want to add the possibility
to define an ognl expression in
