Hi,
I wrote an MBean JUnit TestRunner for JRun 4, which is JMX-based. I did it
for exactly the reasons you described below. I'll see if I can dig it up.
Best,
Scott Stirling
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of James
Higginbotham
Bill
and names.
On a side note, I don't think Marc Fleury is ignorant of these issues. And
certainly Sun is aware of JBoss. So until and unless you get a cease and
desist order or something, I think you can just keep coding.
Best,
Scott Stirling
JRun QA
Macromedia
-Original Message-
From
The term required by Sun J2EE licensing agreements is J2EE compatible not
compliant. For example, JRun 3.1, which passes J2EE CTS and is fully
compliant, has to be marketed as J2EE compatible.
Scott Stirling
JRun QA
Macromedia
-Original Message-
From: Bill Burke [mailto:[EMAIL
Ah, but I see what you mean -- they mixed up Java compatibility and J2EE
compatibility -- quite different things.
Scott Stirling
JRun QA
Macromedia
-Original Message-
From: Scott Stirling
Sent: Wednesday, August 29, 2001 1:50 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-dev
Are you using the latest version of Jikes? Could just be a bug in a an
earlier version.
Scott Stirling
Macromedia
-Original Message-
From: Jason Dillon
To: [EMAIL PROTECTED]
Sent: 8/13/01 10:36 PM
Subject: [JBoss-dev] VerifyError: (class: org/jboss/web/WebServer
Does anyone know why
with JBoss-specific scripts and deployment descriptors.
Scott Stirling
JRun QA
Macromedia
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
