Thanks for taking the time to respond, and for scolding me nicely
:). Sorry about posting to commons-cvs... I meant to post to commons-dev
and simply copied the address from the wrong email.
I'll read up on Bugzilla and report the bug.
Thanks,
Kirk
At 02:08 PM 8/6/2004 -0400, you wrote:
Hi,
First of all, please use [EMAIL PROTECTED] rather than
[EMAIL PROTECTED] for this question.
Enhancements should be submitted in .diff format to Bugzilla at
http://issues.apache.org/bugzilla. See more guidelines at
http://www.apache.org/dev/contributors.html#bugreports.
You're right that Modeler isn't very active at the moment. It's used
fairly widely though, mostly through Tomcat which depends on it. So we
take patch submissions for Modeler seriously and they are committed.
Use the standard Bugzilla approach please, rather than sending personal
emails to any committers. And use [EMAIL PROTECTED] to discuss ideas,
proposals, changes, etc.
As for ObjectReference being of the wrong case: submit that as a bug in
Bugzilla please. Thanks,
Yoav Shapira
Millennium Research Informatics
>-----Original Message-----
>From: Kirk Lund [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 06, 2004 1:58 PM
>To: [EMAIL PROTECTED]
>Subject: [Modeler] objectReference to ObjectReference
>
>I'd like to propose the following change to
>org.apache.commons.modeler.ManagedBean...
>
>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. Should I send an email to this group with the changed
>ManagedBean.java attached?
>
>Modeler doesn't seem very active at present. I'd also like to sweep
>through the src code, adding in javadocs, formatting changes, and
general
>cleanup. Unless someone else is already doing this? If not, then
should I
>attach the code to emails I send to this list or directly to a
>committer? Sorry for all the questions but I'm not sure how everyone
>involved would prefer this, esp. since "jakarta-commons" spans so many
>sub-projects.
>
>Kirk Lund
>GemStone Systems, Inc.
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
