Mark,
Apologies for leaving an answer to your question below blank, I didn't catch it
until now.
> Do you have a bug id for http://bugs.sun.com/ for this issue, because to
> prevent from duplicate reports I tried to search it. But that search function
> in Sun/Oracle bug database is severely b
On Mar 12, 2013, at 1233PM, Mark Brouwer wrote:
>
>
> https://issues.apache.org/jira/browse/RIVER-416 contains a patch against the
> trunk that could be applied, as well as the complete source code. My
> j.u.l.Levels implementation was based on the initial submission from Sun to
> Apache so i
Hi Dennis,
As I had some time to fix my own code as result of the change in the
serialized form of j.u.l.Level I had to look a bit better what has been
going on with j.u.l.Level and how to solve it. As a result I implemented
a more robust solution than that currently in trunk, more about that
Reading the conclusion to this thread, and the JIRA comments around it,
I'm struck by a few things:
1 - At no time did I see anything that read as "you're wrong". All
discussion was about the merits of one approach over another.
1a - A couple of times, people came back with statements that I wou
On Feb 10, 2013, at 404PM, Mark Brouwer wrote:
> Hi Dennis,
>
> On 2/5/13 6:39 PM, Dennis Reedy wrote:
>> This also happens with updates to Java 1.6 (u39). The fix looks to
>> besimple. The Levels class seems to be the issue. Unless I'm missing
>> something, it seems straight forward enough the
Hi Dennis,
BTW I'm glad you reported this issue, because I used these logging
classes from the starter kit in many non Jini projects too and these
are
all likely to blow up soon if people install the latest Java SE, which
I'm
not that happy with.
On 2/11/13 2:20 AM, Dennis Reedy wrote:
Eve
On Feb 10, 2013, at 801PM, Mark Brouwer wrote:
> Hi Dennis,
>
> On 2/10/13 10:39 PM, Dennis Reedy wrote:
>>
>>
>> A few thoughts here:
>>
>
>> 1. Configuring custom levels is done by configuring the custom
>> level'sinteger level value (this can be done for all levels, not just custom
>> lev
Hi Dennis,
On 2/10/13 10:39 PM, Dennis Reedy wrote:
A few thoughts here:
1. Configuring custom levels is done by configuring the custom
level'sinteger level value (this can be done for all levels, not just custom
levels). For example, taking a look at the
examples.hello/config/logging.prop
On Feb 10, 2013, at 404PM, Mark Brouwer wrote:
> Hi Dennis
Hi Mark,
Glad to see your input on the list.
> ,
>
> On 2/5/13 6:39 PM, Dennis Reedy wrote:
>> This also happens with updates to Java 1.6 (u39). The fix looks to
>> besimple. The Levels class seems to be the issue. Unless I'm missing
Hi Dennis,
On 2/5/13 6:39 PM, Dennis Reedy wrote:
This also happens with updates to Java 1.6 (u39). The fix looks to
besimple. The Levels class seems to be the issue. Unless I'm missing
something, it seems straight forward enough the create a custom level
without using the ClassReplacingObjectOu
On Feb 6, 2013, at 918AM, Peter Firmstone wrote:
> On 6/02/2013 11:49 PM, Dennis Reedy wrote:
>> On Feb 5, 2013, at 218PM, Greg Trasuk wrote:
>>>
>>> Actually, could you open a Jira ticket for this and attach your patch?
>>> I suspect that since it's a core library, we might be best to "Review
>
On 6/02/2013 11:49 PM, Dennis Reedy wrote:
On Feb 5, 2013, at 218PM, Greg Trasuk wrote:
Actually, could you open a Jira ticket for this and attach your patch?
I suspect that since it's a core library, we might be best to "Review
then commit" on this one. I agree that a quick release is in orde
On Wed, 2013-02-06 at 08:49, Dennis Reedy wrote:
> On Feb 5, 2013, at 218PM, Greg Trasuk wrote:
> >
> >
> > Actually, could you open a Jira ticket for this and attach your patch?
> > I suspect that since it's a core library, we might be best to "Review
> > then commit" on this one. I agree tha
On Feb 5, 2013, at 218PM, Greg Trasuk wrote:
>
>
> Actually, could you open a Jira ticket for this and attach your patch?
> I suspect that since it's a core library, we might be best to "Review
> then commit" on this one. I agree that a quick release is in order.
> Perhaps we should branch fr
On Feb 5, 2013, at 218PM, Greg Trasuk wrote:
>
>
> On Tue, 2013-02-05 at 12:39, Dennis Reedy wrote:
>> This also happens with updates to Java 1.6 (u39). The fix looks to be
>> simple. The Levels class seems to be the issue. Unless I'm missing
>> something, it seems straight forward enough the
On Tue, 2013-02-05 at 12:39, Dennis Reedy wrote:
> This also happens with updates to Java 1.6 (u39). The fix looks to be simple.
> The Levels class seems to be the issue. Unless I'm missing something, it
> seems straight forward enough the create a custom level without using the
> ClassReplaci
This also happens with updates to Java 1.6 (u39). The fix looks to be simple.
The Levels class seems to be the issue. Unless I'm missing something, it seems
straight forward enough the create a custom level without using the
ClassReplacingObjectOutputStream and the LevelData approach. I modified
Major problem here. With the latest Java update (java version "1.7.0_13") the
following occurs:
Caused by: java.lang.RuntimeException: Unexpected exception
at com.sun.jini.logging.Levels.createLevel(Levels.java:142)
at com.sun.jini.logging.Levels.(Levels.java:52)
... 18 mo
18 matches
Mail list logo
