[
https://issues.apache.org/jira/browse/WW-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594717#comment-14594717
]
ASF GitHub Bot commented on WW-4516:
------------------------------------
GitHub user Naros opened a pull request:
https://github.com/apache/struts/pull/43
WW-4516: Allow JSON plug-in to skip bean cache when devMode is enabled.
Adds support for disabling bean cache on JSON plugin when devMode is
enabled.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Naros/struts master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/struts/pull/43.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #43
----
commit 30df43f1fa01ecbbc021d47cadb3cd759bdba8f9
Author: Naros <[email protected]>
Date: 2015-06-20T18:19:29Z
WW-4516: Allow JSON plug-in to skip bean cache when devMode is enabled.
----
> 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.x
>
>
> 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)
