Re: [JBoss-dev] Why the two jboss logging frameworks?

2004-04-19 Thread Adrian Brock 
I've fixed most of the testsuite, there are still two
modelmbean failures I don't understand.
The descriptor validation part of the spec is voodoo to me.

build test-compliance-JBossMX

Also, I fixed some of the tests to catch the RuntimeOperationsException
thrown by Descriptor.isValid()
But the JMX RI implementation we currently have in our CVS
doesn't throw this exception for 6 of the tests.

build test-compliance-RI

There are also two issues with MLET/classloading in the implementation
tests

build test-implementation

Regards,
Adrian

On Sat, 2004-04-17 at 14:27, Adrian Brock wrote:
 Thomas or Tom,
 
 A lot of the JMX testsuite tests for JBossMX are failing.
 Either the tests should be fixed or the reason why they
 fail analysed.
 Last time I ran it, there were three known issues
 non of them important.
 
 Regards,
 Adrian
 
 On Sat, 2004-04-17 at 14:00, Adrian Brock wrote:
  I'll fix it in both 3.2 and head
  My fault for not keeping head in line.
  
  Regards,
  Adrian
  
  On Sat, 2004-04-17 at 13:42, Adrian Brock wrote:
   The JMX logging framework was removed from 3.2.0 but never
   from head. When Tom backported jmx from head into 3.2.4RC1
   he also copied the old jmx logging framework.
   
   Regards,
   Adrian
   
   On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
In trying to cleanup the logging for bug [ 936465 ] JCA layer has
invalid assumption about Log4jLoggerPlugin
https://sourceforge.net/tracker/index.php?func=detailaid=936465group_i
d=22866atid=376685

I see that we have two seperate frameworks:
jmx org.jboss.mx.logging 
comon org.jboss.logging
 
Is this a legacy issue from before jmx depending on the common module?
There can only
be one jboss logging abstraction.
 

Scott Stark
Chief Technology Officer
JBoss Group, LLC
 
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Inc.
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] Why the two jboss logging frameworks?

2004-04-17 Thread Scott M Stark 
In trying to cleanup the logging for bug [ 936465 ] JCA layer has
invalid assumption about Log4jLoggerPlugin
https://sourceforge.net/tracker/index.php?func=detailaid=936465group_i
d=22866atid=376685

I see that we have two seperate frameworks:
jmx org.jboss.mx.logging 
comon org.jboss.logging
 
Is this a legacy issue from before jmx depending on the common module?
There can only
be one jboss logging abstraction.
 

Scott Stark
Chief Technology Officer
JBoss Group, LLC
 
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Why the two jboss logging frameworks?

2004-04-17 Thread Adrian Brock 
The JMX logging framework was removed from 3.2.0 but never
from head. When Tom backported jmx from head into 3.2.4RC1
he also copied the old jmx logging framework.

Regards,
Adrian

On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
 In trying to cleanup the logging for bug [ 936465 ] JCA layer has
 invalid assumption about Log4jLoggerPlugin
 https://sourceforge.net/tracker/index.php?func=detailaid=936465group_i
 d=22866atid=376685
 
 I see that we have two seperate frameworks:
 jmx org.jboss.mx.logging 
 comon org.jboss.logging
  
 Is this a legacy issue from before jmx depending on the common module?
 There can only
 be one jboss logging abstraction.
  
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
  
  
 
 
 
 ---
 This SF.Net email is sponsored by: IBM Linux Tutorials
 Free Linux tutorial presented by Daniel Robbins, President and CEO of
 GenToo technologies. Learn everything from fundamentals to system
 administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
 ___
 JBoss-Development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Inc.
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Why the two jboss logging frameworks?

2004-04-17 Thread Adrian Brock 
I'll fix it in both 3.2 and head
My fault for not keeping head in line.

Regards,
Adrian

On Sat, 2004-04-17 at 13:42, Adrian Brock wrote:
 The JMX logging framework was removed from 3.2.0 but never
 from head. When Tom backported jmx from head into 3.2.4RC1
 he also copied the old jmx logging framework.
 
 Regards,
 Adrian
 
 On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
  In trying to cleanup the logging for bug [ 936465 ] JCA layer has
  invalid assumption about Log4jLoggerPlugin
  https://sourceforge.net/tracker/index.php?func=detailaid=936465group_i
  d=22866atid=376685
  
  I see that we have two seperate frameworks:
  jmx org.jboss.mx.logging 
  comon org.jboss.logging
   
  Is this a legacy issue from before jmx depending on the common module?
  There can only
  be one jboss logging abstraction.
   
  
  Scott Stark
  Chief Technology Officer
  JBoss Group, LLC
   
   
  
  
  
  ---
  This SF.Net email is sponsored by: IBM Linux Tutorials
  Free Linux tutorial presented by Daniel Robbins, President and CEO of
  GenToo technologies. Learn everything from fundamentals to system
  administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
  ___
  JBoss-Development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Inc.
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Re: [JBoss-dev] Why the two jboss logging frameworks?

2004-04-17 Thread Adrian Brock 
Thomas or Tom,

A lot of the JMX testsuite tests for JBossMX are failing.
Either the tests should be fixed or the reason why they
fail analysed.
Last time I ran it, there were three known issues
non of them important.

Regards,
Adrian

On Sat, 2004-04-17 at 14:00, Adrian Brock wrote:
 I'll fix it in both 3.2 and head
 My fault for not keeping head in line.
 
 Regards,
 Adrian
 
 On Sat, 2004-04-17 at 13:42, Adrian Brock wrote:
  The JMX logging framework was removed from 3.2.0 but never
  from head. When Tom backported jmx from head into 3.2.4RC1
  he also copied the old jmx logging framework.
  
  Regards,
  Adrian
  
  On Sat, 2004-04-17 at 13:25, Scott M Stark wrote:
   In trying to cleanup the logging for bug [ 936465 ] JCA layer has
   invalid assumption about Log4jLoggerPlugin
   https://sourceforge.net/tracker/index.php?func=detailaid=936465group_i
   d=22866atid=376685
   
   I see that we have two seperate frameworks:
   jmx org.jboss.mx.logging 
   comon org.jboss.logging

   Is this a legacy issue from before jmx depending on the common module?
   There can only
   be one jboss logging abstraction.

   
   Scott Stark
   Chief Technology Officer
   JBoss Group, LLC
    

   
   
   
   ---
   This SF.Net email is sponsored by: IBM Linux Tutorials
   Free Linux tutorial presented by Daniel Robbins, President and CEO of
   GenToo technologies. Learn everything from fundamentals to system
   administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
   ___
   JBoss-Development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
-- 
 
Adrian Brock
Director of Support
Back Office
JBoss Inc.
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

RE: [JBoss-dev] Why the two jboss logging frameworks?

2004-04-17 Thread Scott M Stark 

Ok, thanks.


Scott Stark
Chief Technology Officer
JBoss Group, LLC
 
 
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Adrian Brock
 Sent: Saturday, April 17, 2004 6:01 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] Why the two jboss logging frameworks?
 
 I'll fix it in both 3.2 and head
 My fault for not keeping head in line.
 
 Regards,
 Adrian
 



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development