The attached JMeter file appears to be in the NEW format (2.1) not an old format. It opens OK in 2.1.
S, On Apr 8, 2005 10:43 PM, Carsten Sensler <[EMAIL PROTECTED]> wrote: > Hello together, > I has the same problem that I cannot open old JMX files with the JMeter > version 2.03. I get the same error message. > > The log file excerpt looks as follows: > > 2005/04/08 23:35:38 ERROR - jmeter.save.SaveService: Problem loading part of > file org.apache.avalon.framework.configuration.ConfigurationException: No > attribute named "class" is associated with the configuration element > "testelement" at - > at > org.apache.avalon.framework.configuration.DefaultConfiguration.getAttribute( > DefaultConfiguration.java:279) > at > org.apache.jmeter.save.SaveService.createTestElement(SaveService.java:960) > at > org.apache.jmeter.save.SaveService.generateNode(SaveService.java:1137) > at > org.apache.jmeter.save.SaveService.loadSubTree(SaveService.java:933) > at org.apache.jmeter.gui.action.Load.doAction(Load.java:97) > at > org.apache.jmeter.gui.action.ActionRouter.performAction(ActionRouter.java:81 > ) > at > org.apache.jmeter.gui.action.ActionRouter.access$000(ActionRouter.java:44) > at > org.apache.jmeter.gui.action.ActionRouter$1.run(ActionRouter.java:62) > at java.awt.event.InvocationEvent.dispatch(Unknown Source) > at java.awt.EventQueue.dispatchEvent(Unknown Source) > at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown > Source) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown > Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.run(Unknown Source) > > The format of "my" JMX files is to be worked on more clearly and more > pleasantly, as the current format. > Is it to be integrated possible a converter or such a utility in the > JMeter?? > > I attached a script in the better format as example times. > > Best thanks and kind regards from Germany, > Carsten > > > -----Urspr�ngliche Nachricht----- > > Von: sebb [mailto:[EMAIL PROTECTED] > > Gesendet: Freitag, 8. April 2005 15:19 > > An: JMeter Users List > > Betreff: Re: JMX not working anymore in new JMeter version > > > > In theory I think it is possible to transform the 2.1 format into 2.0 > > using XSLT, but no-one has addressed this. > > > > But why do you need to go back to 2.0.3? > > > > I know 2.1 has not been formally released, but if you have been using > > it for some while, presumably it mostly meets your needs? > > > > If not, please let us know so it can be addressed. > > > > I think all the 2.0.3 functionality is now in 2.1, but there is a > > little more work required before we can make a formal release. > > > > S. > > On Apr 8, 2005 1:45 PM, Sander Stevens <[EMAIL PROTECTED]> wrote: > > > Hmmm, ok, clear. But is there a way to go back and use 2.0.3 again with > > > my 2.1 jmx files? > > > > > > Sander > > > > > > -----Original Message----- > > > From: Peter Lin [mailto:[EMAIL PROTECTED] > > > Sent: vrijdag 8 april 2005 14:42 > > > To: JMeter Users List > > > Subject: Re: JMX not working anymore in new JMeter version > > > > > > the difference is 2.1 or nightly builds use XStream to save jmx files. > > > it's faster and more efficient. basically, the format is different. > > > > > > peter > > > > > > On Apr 8, 2005 8:38 AM, Sander Stevens <[EMAIL PROTECTED]> wrote: > > > > OK, I asked around and this is the story: > > > > > > > > We are using version 2.1. I didn't know that version existed, but > > > > obviously someday it was available on the download site. Problem is > > > > (probably) that some functionality is available in 2.1, but not in > > > > 2.0.x. If I know what to change or remove, I can continue. But I > > > really > > > > don't have a clue what's different. > > > > > > > > Anybody? > > > > > > > > Sander > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
