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 OGNL inside your component to parse something, you do have to use the Ognl.getValue() method(s). You'll have to manually break apart that expression first and parse the "subparts" based on the comma separator(s). It would be nice if the hivemind.ObjectTranslator service weren't private. Then, you could just pass in 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 users Subject: OGNL in own component 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 the "properties" parameter like in the contribTable component. I've used the Ognl.getValue() method so far but this doesn't seem to work with something like: ... properties="id:id, date:page.convertDate(date)" ... I tried to use Ognl.parseExpression() and the ExpressionEvaluator provided by Tapestry and used in contribTable but it didn't work :-( My question is now how to enable my component to handle such ognl expressions in the "properties" parameter? Thanks! Andreas --------------------------------------------------------------------- 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]
