river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Gibson (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 Fri, 22 Feb 2013 13:42:13 GMT

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

Robert Gibson commented on RIVER-416:
-------------------------------------

2 small corrections:
1) The name field *does* get correctly populated with the suggested approach (as per the Javadoc
and my experiments at least, maybe you tried on a buggy JRE?)
2) I wasn't thinking so much of serialisation/deserialisation by code using different versions
of River, but rather deserialisation by code that is River-independent. Currently, logging
code can receive LogRecord objects with level == Levels.HANDLED or Levels.FAILED without having
a dependence on jsk-dl.jar, since it is just a java.util.logging.Level object. So, introducing
the custom subclass would mean that, for example, a log framework which current only has dependencies
on java.util would now have to have jsk-dl.jar available to it.

I think the edge might be wider than you imagine ;)
                
> 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