[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Dimitris Andreadis (andd) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-28 22:00 Message: Logged In: YES user_id=583305 jdk5 ModelMBeanInfoSupport.getDescriptors(ALL) does NOT return the MBean descriptor, so the code was changed to get it explicitly. Reported as SunBug: 343370 -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-25 14:58 Message: Logged In: YES user_id=583305 The DescriptorSupport/ModelMBeanInfoSupport classes of jdk5 do copy on get/set, while jboss doesn't. So when the persistence interceptor gets called metadata (like OnUpdate) have been lost, but I can't find where/when. I can imagine there may be deeper implications because of this. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 18:46 Message: Logged In: YES user_id=583305 Just checked running the same jmx tests with the jdk5 java.management.* classes removed and they pass. There are also 8 failures in the jbossmx testsuite (with jdk5) so maybe that's a starting point, too. The tests under the jmx module present many failures but it seems they are not maintained for some time now. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 18:14 Message: Logged In: YES user_id=175228 We are running the tests against java5 now. We just need to continue to drill down into where the jmx implementation is causing issues and continue to isolate reliance on the jboss implementation details. I'm working on the 4.0 and 3.2 java 5 testsuite runs so I'll look at this test. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:56 Message: Logged In: YES user_id=583305 org.jboss.test.jmx.test.DeployXMBeanUnitTestCase: testUserXMBeanPersistentValues testUserXMBeanPersistentValuesWithCustomPM both fail (on HEAD) with jdk5. I haven't checked if those pass with jdk1.4 I found out though, by not being able to deploy docs/examples/jmx/persistent-service. I wonder now, what should be the next step, i.e. how to check for incopatibilities. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 17:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 17:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Scott M Stark (starksm) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-25 14:58 Message: Logged In: YES user_id=583305 The DescriptorSupport/ModelMBeanInfoSupport classes of jdk5 do copy on get/set, while jboss doesn't. So when the persistence interceptor gets called metadata (like OnUpdate) have been lost, but I can't find where/when. I can imagine there may be deeper implications because of this. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 18:46 Message: Logged In: YES user_id=583305 Just checked running the same jmx tests with the jdk5 java.management.* classes removed and they pass. There are also 8 failures in the jbossmx testsuite (with jdk5) so maybe that's a starting point, too. The tests under the jmx module present many failures but it seems they are not maintained for some time now. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 18:14 Message: Logged In: YES user_id=175228 We are running the tests against java5 now. We just need to continue to drill down into where the jmx implementation is causing issues and continue to isolate reliance on the jboss implementation details. I'm working on the 4.0 and 3.2 java 5 testsuite runs so I'll look at this test. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:56 Message: Logged In: YES user_id=583305 org.jboss.test.jmx.test.DeployXMBeanUnitTestCase: testUserXMBeanPersistentValues testUserXMBeanPersistentValuesWithCustomPM both fail (on HEAD) with jdk5. I haven't checked if those pass with jdk1.4 I found out though, by not being able to deploy docs/examples/jmx/persistent-service. I wonder now, what should be the next step, i.e. how to check for incopatibilities. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 17:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 17:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Nobody/Anonymous (nobody) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 13:21 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Nobody/Anonymous (nobody) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 15:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Nobody/Anonymous (nobody) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 17:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 05:21 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Nobody/Anonymous (nobody) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 07:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 07:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 07:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Nobody/Anonymous (nobody) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:56 Message: Logged In: YES user_id=583305 org.jboss.test.jmx.test.DeployXMBeanUnitTestCase: testUserXMBeanPersistentValues testUserXMBeanPersistentValuesWithCustomPM both fail (on HEAD) with jdk5. I haven't checked if those pass with jdk1.4 I found out though, by not being able to deploy docs/examples/jmx/persistent-service. I wonder now, what should be the next step, i.e. how to check for incopatibilities. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 17:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 17:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 05:21 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Scott M Stark (starksm) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 08:14 Message: Logged In: YES user_id=175228 We are running the tests against java5 now. We just need to continue to drill down into where the jmx implementation is causing issues and continue to isolate reliance on the jboss implementation details. I'm working on the 4.0 and 3.2 java 5 testsuite runs so I'll look at this test. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 07:56 Message: Logged In: YES user_id=583305 org.jboss.test.jmx.test.DeployXMBeanUnitTestCase: testUserXMBeanPersistentValues testUserXMBeanPersistentValuesWithCustomPM both fail (on HEAD) with jdk5. I haven't checked if those pass with jdk1.4 I found out though, by not being able to deploy docs/examples/jmx/persistent-service. I wonder now, what should be the next step, i.e. how to check for incopatibilities. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 07:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 07:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 07:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-1071690 ] XMBean persistence doesn't work with jdk5 runtime
Bugs item #1071690, was opened at 2004-11-23 15:21 Message generated for change (Comment added) made by andd You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 Category: JBossMX Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Dimitris Andreadis (andd) Assigned to: Scott M Stark (starksm) Summary: XMBean persistence doesn't work with jdk5 runtime Initial Comment: XMBean persistence doesn't work when using a jdk5 runtime for 3.2.x 4.0.x and HEAD (it works fine under jdk 1.3/1.4) This applies to both the old ObjectStreamAttributePersistenceManager and the new DelegatingPersistenceManager. It seems this is not a problem of the PMs since they are never called to store () attributes. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 18:46 Message: Logged In: YES user_id=583305 Just checked running the same jmx tests with the jdk5 java.management.* classes removed and they pass. There are also 8 failures in the jbossmx testsuite (with jdk5) so maybe that's a starting point, too. The tests under the jmx module present many failures but it seems they are not maintained for some time now. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 18:14 Message: Logged In: YES user_id=175228 We are running the tests against java5 now. We just need to continue to drill down into where the jmx implementation is causing issues and continue to isolate reliance on the jboss implementation details. I'm working on the 4.0 and 3.2 java 5 testsuite runs so I'll look at this test. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:56 Message: Logged In: YES user_id=583305 org.jboss.test.jmx.test.DeployXMBeanUnitTestCase: testUserXMBeanPersistentValues testUserXMBeanPersistentValuesWithCustomPM both fail (on HEAD) with jdk5. I haven't checked if those pass with jdk1.4 I found out though, by not being able to deploy docs/examples/jmx/persistent-service. I wonder now, what should be the next step, i.e. how to check for incopatibilities. -- Comment By: Scott M Stark (starksm) Date: 2004-11-23 17:47 Message: Logged In: YES user_id=175228 Is there a testcase which shows the failure under 5.0? The only way to force the use of our implementation is the bootclasspath and this is not a general option. -- Comment By: Dimitris Andreadis (andd) Date: 2004-11-23 17:41 Message: Logged In: YES user_id=583305 So I made an edited version of jdk5/jre/rt.jar with all javax.management classes removed, and the damned thing worked. There may be incopatibilities between our javax.management.* and jdk5 javax.management. Is there a way to force our javax.management classes to be used, instead? (setting javax.management.builder.initial obviously has no impact on the javax.management classes) -- Comment By: Adrian Brock (ejort) Date: 2004-11-23 17:18 Message: Logged In: YES user_id=9459 This will be one of two things: 1) You are using RequiredModelMBean directly which in java5 will use Sun's modelmbean implementation rather XMBean 2) There is something incompatible happening with the descriptor which is held in Sun's ModelMBeanInfo/ModelMBeanAttributeInfo implementation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=1071690group_id=22866 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
