Creating a custom Introspector is exactly what you need to do.
For example, someone in the last month or two made one that queries Lucene indices.
WILL
----- Original Message ----- From: "Jason R Briggs" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 16, 2005 2:58 PM
Subject: a question about extending velocity
Hi
I have a requirement for using jython with velocity, and -- as far as it stands -- it's not usable without either putting some nasty looking method calls directly in the template, or creating a tool to handle jython object properties/methods. I'm not keen on either method. I notice some traffic on this in the past but haven't found any patches or tools to do what I want.
I also haven't come across any documentation that says what is the accepted way to extend velocity for handling introspection of non-standard object types.
As far as I can figure, you are able to set the UBERSPECT_CLASSNAME property on VelocityEngine to a custom uberspect implementation, in order to add functionality to the standard UberspectImpl (which seems to work fine), but have I missed something? Is there a better/accepted approach to doing this?
Thx, Jason
--------------------------------------------------------------------- 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]
