struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukasz Lenart (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (WW-4516) BeanInfo caching does not work when using Hotswap/Rapid-development tools.
Date Fri, 26 Jun 2015 19:47:04 GMT

     [ https://issues.apache.org/jira/browse/WW-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukasz Lenart resolved WW-4516.
-------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.5.x)
                   2.5

PR applied, thanks!

> BeanInfo caching does not work when using Hotswap/Rapid-development tools.
> --------------------------------------------------------------------------
>
>                 Key: WW-4516
>                 URL: https://issues.apache.org/jira/browse/WW-4516
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Plugin - JSON
>    Affects Versions: 2.3.24
>            Reporter: Chris Cranford
>            Priority: Critical
>             Fix For: 2.5
>
>
> WW-3902 added functionality to cache BeanInfo instances that were retrieved by introspection
to avoid application server locks.  
> The problem with this fix is that when using rapid-development or hotswap tools like
JRebel, changes to the JSON output is unaffected because the plugin doesn't see bean changes
due to it's internal cache.
> It would probably be ideal that when struts.devMode is enabled, the plugin bypasses the
internal cache that it does to support development tools such as JRebel and only use the caching
mechanism non-development cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message