There were couple incidences in the past where gmbal integration in v3 and  webservices was out of sync'd.  I don't remember if QL caught the issue. 
Can someone from the webservices team confirm that it's okay to integetrate gmbal version 3.0.0-b019 with webservices version 2.0-b23.

Thanks,
Jane

Lloyd Chambers wrote:

Doesn't QuickLook pick up such issues?

Is there a way to make it do so?

On Oct 15, 2009, at 9:02 AM, Jane Young wrote:

Hi Jennifer,

Please make sure webservices is referencing the same gmbal api.

Thanks,
Jane


Jennifer Chou wrote:

Fixes:

• Issue 9164 :
• Added code to use doPrivileged  around reflective calls.
• Issue 10229:
• Fixed JMXRegistrationManager to avoid duplicate registration attempt on root when AMX is already running.
• Cleaned up some locking issues in JMXRegistrationManager.

Index: pom.xml
===================================================================
--- pom.xml     (revision 32792)
+++ pom.xml     (working copy)
@@ -153,7 +153,7 @@
         <jersey.version>1.1.3-ea</jersey.version>
         <jbi.version>1.0</jbi.version>
         <wsdl4j.version>1.6.2</wsdl4j.version>
-        <gmbal.version>3.0.0-b018</gmbal.version>
+        <gmbal.version>3.0.0-b019</gmbal.version>
         <glassfish-management-api.version>3.0.0-b010</glassfish-management-api.
version>
         <mimepull.version>1.4</mimepull.version>
         <findbugs.exclude></findbugs.exclude>

Lloyd Chambers

lloyd.chambers@sun.com

GlassFish Team