Well apparently the closure of the referenced object graph is including QName due to an object holding onto an XML element or the like, and the client and server don't agree on the definition of javax.xml.namespace.QName.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Matt Munz" <[EMAIL PROTECTED]> To: "JBoss Developers Group" <[EMAIL PROTECTED]> Sent: Thursday, November 07, 2002 11:35 AM Subject: [JBoss-dev] JMX-RMI headaches > Hi all, > > For unit tests, I thought the RMI adaptor might be easier than JMX-NET. > Unfortunately, I've been running into some snags... > > When I try to message an MBean, that takes a Vector parameter, over the > RMI adaptor, I get the exception below. What is confusing to me is that I > don't use QNames at all. Why is the adaptor complaining about an object I > don't even use (it is on the classpath)? > > Is there an easier solution than RMI for remote access to the MBeans in > the server? > > TIA. > > - Matt Munz > > [junit] Error unmarshaling return; nested exception is: > [junit] java.io.InvalidClassException: javax.xml.namespace.QName; > local class incompatible: stream classdesc ser > ialVersionUID = -9120448754896609940, local class serialVersionUID > = -5673018430892733549 ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
