Hi Eric, > 3) When should I declare a VelPropertyGet not cacheable? I'm just guessing, but maybe when you don't want to reuse the same VelPropertyGet when you are processing the same template again. ASTIdentifier#execute is where it's being cached.
> 4) Different properties in my target class are accessed via different > chains of method calls. Thus far, my custom getPropertyGet instantiate > one type of VelPropertyGet, whose invoke() runs a conditional on the > property name to return the right value. > > Would it be better to check the property name inside getPropertyGet and > write more VelPropertyGet classes, returning a VelPropertyGet > customized for a particular chain of method calls. > > [another way of phrasing this might be 'does Velocity cache the > VelPropertyGets on a per-class or per-property basis? It looks like a per-identifier basis. Again, ASTIdentifier. ## Somebody correct me on this. I'm likely to be wrong. B) Best regards, -- Shinobu Kawai -- Shinobu Kawai <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
