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=detail&atid=376685&aid=1071690&group_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=detail&atid=376685&aid=1071690&group_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
