[
https://issues.apache.org/jira/browse/WW-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14595946#comment-14595946
]
ASF GitHub Bot commented on WW-4516:
------------------------------------
Github user Naros commented on a diff in the pull request:
https://github.com/apache/struts/pull/43#discussion_r32936125
--- Diff: plugins/json/src/main/java/org/apache/struts2/json/JSONUtil.java
---
@@ -53,7 +68,22 @@
* @throws JSONException
*/
public static String serialize(Object object) throws JSONException {
--- End diff --
It is currently used in the test cases
JSONResultTest - testJSONUtilNPEOnNullMethod()
JSONUtilTest = testSerializeDeserialize()
Thoughts?
> 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)
