[ 
https://issues.apache.org/jira/browse/WW-5124?focusedWorklogId=649768&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-649768
 ]

ASF GitHub Bot logged work on WW-5124:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Sep/21 21:43
            Start Date: 12/Sep/21 21:43
    Worklog Time Spent: 10m 
      Work Description: JCgH4164838Gh792C124B5 commented on pull request #489:
URL: https://github.com/apache/struts/pull/489#issuecomment-917715659


   The latest push fixed the previous failure in the build, but now there are 
two failures reported in `DefaultDispatcherErrorHandlerTest` 
(`testHandleErrorIllegalStateException()`, `testHandleErrorIOException()`).  
The failure reported is the same for both: "Unexpected method call 
HttpServletResponse.setContentType("text/html").".
   
   This does not make sense to me, as neither `DefaultDispatcherErrorHandler` 
nor its unit test was changed in the PR.  When I build this locally (Windows 
10, Oracle JDK7 or OpenJDK 11), there are no failures, and manual builds 
complete normally against the PR's Git branch.
   
   Maybe it is happening due to something with the automated build environment 
(or Linux vs. Windows) ?


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 649768)
    Time Spent: 2h 20m  (was: 2h 10m)

> 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.6, 2.5.28
>
>          Time Spent: 2h 20m
>  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)

Reply via email to