>If we want to release Struts-EL with 1.1, I guess we'll have to advise >users to turn off tag pooling in their containers. Will that work?
Tag reuse is not directly tied to tag pooling. Do all containers let you control these things, in any case? >If I now clearly understand how this works (we'll see), I think I know >how to fix this, but it will take considerable manual labor. In short, >I'll have to change the source code for every EL tag class, and every EL >tag BeanInfo class, adding "shadow" attributes and getters/setters for >every tag attribute. Although this will be a lot of typing, it's very >straightforward. It seems like it might work to simply save the values of the set attributes for which there are EL expr on entry to doStartTag and then restore the values as the last line in doEndTag. This will also be tedious but it sounds like less work than what you mention. Not sure if this is fully in the spirit of writing clean tag handlers, but I don't see why it wouldn't work. evaluateExpressions could be enhanced in each tag to save the needed attributes in a Map and another helper method could restore from the Map. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
