You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2004/08/09 20:21:10 UTC

DO NOT REPLY [Bug 30547] New: - ManagedBean uses the wrong case for ObjectReference

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30547>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30547

ManagedBean uses the wrong case for ObjectReference

           Summary: ManagedBean uses the wrong case for ObjectReference
           Product: Commons
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Modeler
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: apache@the9muses.net
                CC: apache@the9muses.net


We are using MX4J with Modeler and decided to use instances of
javax.management.modelmbean.RequiredModelMBean instead of
org.apache.commons.modeler.BaseModelMBean.

MX4J's implementation enforces the use of "ObjectReference" as it's only
supported managed resource type.  This enforcement includes the case of the
string.  Modeler's ManagedBean uses "objectReference" (line 391), and so MX4J's
RequiredModelMBean rejects it, throwing an Exception.

Page 88 of the JMX spec specifies "ObjectReference" as the proper case to be used.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org