[
https://issues.apache.org/jira/browse/RIVER-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584274#comment-13584274
]
Robert Gibson commented on RIVER-416:
-------------------------------------
BTW, to get the name field correctly populated you need to first of all make
sure the level is known, maybe you skipped a line of code and that is why you
weren't seeing it set correctly?
{code}
// Creates a registers as "known" a new Level
new CustomLevel(name, value, resourceBundleName);
// Returns a level corresponding to the just-created on (Level or
CustomLevel depending on JDK version)
final Level parse = Level.parse (Integer.toString (value));
{code}
It's all a bit of a faff, I don't understand why Sun didn't just give us a
constructor ...
> 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
>
>
> 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
