[
https://issues.apache.org/jira/browse/WW-5124?focusedWorklogId=610534&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-610534
]
ASF GitHub Bot logged work on WW-5124:
--------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/21 08:02
Start Date: 14/Jun/21 08:02
Worklog Time Spent: 10m
Work Description: lukaszlenart commented on pull request #489:
URL: https://github.com/apache/struts/pull/489#issuecomment-860245983
This is astonish work 👏 Yet I have some concerns about potentially breaking
backward compatibility, is there a chance/way to make this configurable? To
have a flag to enable tag pooling support if needed?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 610534)
Time Spent: 1h (was: 50m)
> Tag attribute values cached
> ---------------------------
>
> Key: WW-5124
> URL: https://issues.apache.org/jira/browse/WW-5124
> Project: Struts 2
> Issue Type: Bug
> Environment: Here you have a repo that reproduce this:
> https://github.com/dfliess/struts2-tagpooling-bug
> Reporter: Diego Alejandro Fliess
> Priority: Major
> Fix For: 2.5.27, 2.6
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> On some application servers, like glassfish, when handling jsp tag pooling,
> attribute values are cached or not reinitiallized.
> For example:
> {code:java}
> <s:textfield size="50">
> <jsp:attribute name="placeholder">THIS TEXTFIELD SHOULD HAVE
> VALUE</jsp:attribute>
> <jsp:attribute name="value">VALUE</jsp:attribute>
> </s:textfield>
> <s:textfieldsize="50">
> <jsp:attribute name="placeholder">THIS TEXT FIELD SHOULDN'T HAVE
> VALUE</jsp:attribute>
> </s:textfield>{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
