I recently experimented with replacing JMeter save/load code with xstream's java xml serialization code. I'm wondering how people feel about it.
The advantage is the code is 100% simpler. 5 lines of code replace the hundreds currently living in SaveService. The disadvantage is that, without customization, the xstream version of the files are 3-4x larger. Speed, however, appears unchanged. On my local system, JMeter can load both previous versions and xstream versions, so that's not an issue. Also, I would include file versioning with it so that a test plan file would include the jmeter version that made it. This would help in the future with backwards compatibility. I personally like it, but then, a file going from 100k to 400k is no big deal to me - I don't save 10000 objects in my test plans (100 and 400 are the relative sizes of the guitest.jmx file) Any opinions? -- Michael Stover <[EMAIL PROTECTED]> Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
