[jira] [Commented] (WW-4516) BeanInfo caching does not work when using Hotswap/Rapid-development tools.

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WW-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952972#comment-14952972 ] 

Hudson commented on WW-4516:
----------------------------

SUCCESS: Integrated in Struts-JDK7-master #371 (See [https://builds.apache.org/job/Struts-JDK7-master/371/])
WW-4516: Allow JSON plug-in to skip bean cache when devMode is enabled. (crancran.git: rev 30df43f1fa01ecbbc021d47cadb3cd759bdba8f9)
* plugins/json/src/main/java/org/apache/struts2/json/JSONWriter.java
* plugins/json/src/main/java/org/apache/struts2/json/JSONResult.java
* plugins/json/src/main/java/org/apache/struts2/json/JSONUtil.java


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