river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Reedy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIVER-416) The com.sun.jini.logging.Levels class produces a RuntimeException with the latest version of Java
Date Thu, 21 Feb 2013 19:42:12 GMT

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

Dennis Reedy commented on RIVER-416:
------------------------------------

An issue with this approach is the is name field never gets properly populated. Perhaps sing
reflection to set the name field accessible would work as well.

{code}
final Level parsed = Level.parse(Integer.toString(value));
if (parsed.getClass().equals (Level.class)) {
    try {
        Field nameField = parsed.getClass().getField("name");
        nameField.setAccessible(true);
        nameField.set(parsed, name);
    } catch (Exception e) {
        throw new RuntimeException("Unexpected exception", e);
    }
    return parsed;
} else {
    return new CustomLevel(name, value, resourceBundleName);
}
{code}
                
> 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

Mime
View raw message