Geir Magnusson Jr. wrote:
Yes. I have some docs that need to be put in SVN - I hope to do that
today. Once we do that, we need to simply vote to accept the code.
If you start working with it ahead of time, that will be good :)
geir
Are we ready to vote yet? I can't hold my breath much
Why not write LogManager.getLoggingMXBean like this:
return com.ibm.lang.management.ManagementUtils.getLoggingBean();
Yes, it also possible, but tightly binds logging module to
lang-managment implementation.
I found the problem about StackTraceElement when I used luni-kernel.jar
(in
On 10/5/06, Andrey Yakushev [EMAIL PROTECTED] wrote:
I've tried to follow you suggestions. The result:
1. The fix for unimplemented
java.util.logging.LogManager.getLoggingMXBean could be simple, like:
return LoggingMXBeanImpl.getInstance()
But it bind logging module to LoggingMXBean
I've tried to follow you suggestions. The result:
1. The fix for unimplemented
java.util.logging.LogManager.getLoggingMXBean could be simple, like:
return LoggingMXBeanImpl.getInstance()
But it bind logging module to LoggingMXBean implementation.
Probably more clean solution would be:
Do I understand correctly, that j.l.management support could be
implemented for DRLVM as follows:
1. Integrate HARMONY-1407 into classlib and obtain
UnsatisfiedLinkError on DRLVM.
2. Implement native methods in kernel classes as stubs returning some
realistic values. It could allow test and
Andrey Yakushev wrote:
Do I understand correctly, that j.l.management support could be
implemented for DRLVM as follows:
1. Integrate HARMONY-1407 into classlib and obtain
UnsatisfiedLinkError on DRLVM.
2. Implement native methods in kernel classes as stubs returning some
realistic values.
Yes. I have some docs that need to be put in SVN - I hope to do that
today. Once we do that, we need to simply vote to accept the code.
If you start working with it ahead of time, that will be good :)
geir
Nathan Beyer wrote:
Are there any documents or anything that needs to be resolved
Are there any documents or anything that needs to be resolved before I can
start working on the code in HARMONY-1407?
http://issues.apache.org/jira/browse/HARMONY-1407
-Nathan
As I know so far, there is only java code in HARMONY-1407
So, you can build the code on RI, Harmony(only fail on a signal bug of
java.lang.StackTraceElement in luni-kernel.jar), and IBM JDK successfully.
But the native code of j.l.management is not available now, so you'll fail
if you run the
Great!
With java.lang.management and java.lang.instrument it looks like the VM
supporting side is JVMTI for the most part of the functionality. This is the
code I am trying to improve in DRLVM.
On Friday 08 September 2006 14:58 Mikhail Loenko wrote:
Cool!
2006/9/8, George Harley (JIRA)
Cool!
2006/9/8, George Harley (JIRA) [EMAIL PROTECTED]:
Contribution of Java code for package java.lang.management
--
Key: HARMONY-1407
URL: http://issues.apache.org/jira/browse/HARMONY-1407
Yeah! It seems we will have something to manage with our management
console soon. :-)
With Best Regards,
2006/9/8, Mikhail Loenko [EMAIL PROTECTED]:
Cool!
2006/9/8, George Harley (JIRA) [EMAIL PROTECTED]:
Contribution of Java code for package java.lang.management
George Harley (JIRA) wrote:
Contribution of Java code for package java.lang.management
--
Key: HARMONY-1407
URL: http://issues.apache.org/jira/browse/HARMONY-1407
Project: Harmony
13 matches
Mail list logo
