Bugs item #1052254, was opened at 2004-10-22 17:45
Message generated for change (Comment added) made by andd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1052254&group_id=22866

Category: JBossMX
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Janny Buh (janny_buh)
Assigned to: Dimitris Andreadis (andd)
Summary: XMBean 1.0 parsing notification bug

Initial Comment:
I'm using JBoss 3.2.6 and I'm working with XMBean xml
descriptors generated by XDoclet.
I've noticed that when I build a ModelMBeanInfo from an
xml file, the JBossXMBean10 class used to parse the
file ignores the notification section.
I've inspected the source code and I've decteded two
errors regarding notification parsing.

The first is a misspelling in notification tag name
(notificationS instead of notification, as reported in
the jboss_xmbean_1_0.dtd file).

The second is an array class casting error during
conversion from List to Array (I've manually converted
each element, perhaps there is a more elegant solution
for this).

I've attached a possible fix for these bugs.
These bugs also affect JBoss 3.2.x and JBoss 4.0.0.

----------------------------------------------------------------------

>Comment By: Dimitris Andreadis (andd)
Date: 2004-10-29 00:07

Message:
Logged In: YES 
user_id=583305

Bug fixed on 3.2/4.0/HEAD

Thanks for the good report!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1052254&group_id=22866


-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to