Well, if you use Ant-Contrib's var and side-step property immutability altogether the problem is moot then, no? In any case, there's no need for entities. Easier on the eye to simply use an explicit prefix. Of course one runs the risk of <c:var> overriding an existing 'real' property, but any prefix specific enough, for example the macro name limits this risk.
Another option is to use the <define> element added to <macrodef> by Peter on Jose's proposal, which I re-discovered reading the code. Generates a unique attribute name to be used in property names (and references to these properties). --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
