Thanks jeff,
marcf
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jeff Haynie
Sent: Saturday, January 03, 2004 11:25 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JMX 1.2, remoting, and jmx-remoting
commited to 3.2 branch
OK, I
I'll be looking into the new errors today as well as validating these
changes.
The UnifiedClassLoader from head implements the byte code translator
interface
when it should not so I'm removing this.
The byte code translator interface also needs to be updated to be
compatible with
the JSR163
Tom/Scott,
The modules remoting and jmx-remoting weren't integrated into the main
build and weren't being built into the main distribution. I fixed this
and also setup the default detector/connectors to be automatically
deployed as part of the default jboss-service.xml.
I've committed this
, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Haynie
Sent: Saturday, January 03, 2004 7:45 AM
To: [EMAIL PROTECTED]
Cc: Tom Elrod
Subject: Re: [JBoss-dev] JMX 1.2, remoting, and jmx-remoting commited to
3.2 branch
Tom
, 2004 7:45 AM
To: [EMAIL PROTECTED]
Cc: Tom Elrod
Subject: Re: [JBoss-dev] JMX 1.2, remoting, and jmx-remoting commited to
3.2 branch
Tom/Scott,
The modules remoting and jmx-remoting weren't integrated into the main
build and weren't being built into the main distribution. I fixed this
and also setup
, January 03, 2004 7:45 AM
To: [EMAIL PROTECTED]
Cc: Tom Elrod
Subject: Re: [JBoss-dev] JMX 1.2, remoting, and jmx-remoting commited to
3.2 branch
Tom/Scott,
The modules remoting and jmx-remoting weren't integrated into the main
build and weren't being built into the main distribution. I fixed
