You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/03/12 23:21:13 UTC
[jira] [Commented] (RIVER-416) The com.sun.jini.logging.Levels
class produces a RuntimeException with the latest version of Java
[ https://issues.apache.org/jira/browse/RIVER-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600561#comment-13600561 ]
Hudson commented on RIVER-416:
------------------------------
Integrated in River-trunk-jdk7 #148 (See [https://builds.apache.org/job/River-trunk-jdk7/148/])
RIVER-416: Improved robustness of Levels serialization (Revision 1455692)
Result = ABORTED
dreedy : http://svn.apache.org/viewvc/?view=rev&rev=1455692
Files :
* /river/jtsk/trunk/src/com/sun/jini/logging/Levels.java
> The com.sun.jini.logging.Levels class produces a RuntimeException with the latest version of Java
> -------------------------------------------------------------------------------------------------
>
> Key: RIVER-416
> URL: https://issues.apache.org/jira/browse/RIVER-416
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_logging
> Affects Versions: River_2.2.0
> Reporter: Dennis Reedy
> Priority: Blocker
> Attachments: Levels.java, Levels.java, Levels.patch
>
>
> The com.sun.jini.logging.Levels class produces a RuntimeException with the latest version of Java (both 1.6 and 1.7). The issue surrounds creation of custom java.util.logging.Level. The current implementation uses a ClassReplacingObjectOutputStream and the LevelData approach. By removing this approach and creating a subclass of java.util.logging.Level the issue gets resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira