[jboss-jira] [JBoss JIRA] Updated: (JBRULES-976) ShadowProxyUtils.cloneObject() spews noise to stdout

[Dirk Bergstrom (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBRULES-976?page=all ]

Dirk Bergstrom updated JBRULES-976:
-----------------------------------

    Attachment: diff.txt

Patch to fix common exceptions and silence spurious output.

> ShadowProxyUtils.cloneObject() spews noise to stdout
> ----------------------------------------------------
>
>                 Key: JBRULES-976
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-976
>             Project: JBoss Rules
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: Reteoo
>    Affects Versions:  4.0.0.MR4
>            Reporter: Dirk Bergstrom
>         Assigned To: Mark Proctor
>         Attachments: diff.txt
>
>
> With this new code, I get about 75 megs worth of the following errors
> when I initialize my application (stacktraces abbreviated):
> java.lang.IllegalAccessException: Class org.drools.util.ShadowProxyUtils can not access a member of class java.util.Collections$EmptySet with modifiers "private"
>         at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
>         at java.lang.Class.newInstance0(Class.java:344)
>         at java.lang.Class.newInstance(Class.java:303)
>         at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
> java.lang.InstantiationException: java.util.Collections$UnmodifiableSet
>         at java.lang.Class.newInstance0(Class.java:335)
>         at java.lang.Class.newInstance(Class.java:303)
>         at org.drools.util.ShadowProxyUtils.cloneObject(ShadowProxyUtils.java:54)
> The attached patch takes care of these two errors, and removes the
> printStackTrace() call from the catch block, since it's noise to
> everyone except the Drools developers.  If there's a debug or
> developer flag of some kind in the codebase, it would be reasonable to
> use that to control the output.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira