Interesting. I did not realise we were using the default Java libraries to do any of the parsing or output in the 2.0.x series - I thought it was all done via xalan and commons config etc.
This might mean that the TestPlans are also re-ordered. Of couse, the output is still functionally identical, and should only affect things such as regexes, but it's a nuisance. It would be nice if we could force a fixed output ordering, but I'm not sure that this is possible. S. On Apr 7, 2005 9:22 AM, Sonam Chauhan <[EMAIL PROTECTED]> wrote: > Hello JMeter pantheon: > > The XML generated in JMeter logfiles changes when a (very slightly) > different JVM is used: > > JMeter Logfile with Sun JRE 1.4.2_02: > <sampleResult timeStamp="..." dataType="..." threadName="..." label="..." > time="..." responseMessage="..." responseCode="..." success="..."/> > > JMeter Logfile with Sun JRE 1.4.2_08 shows different ordering of the log > attributes: > <sampleResult threadName="..." responseMessage="..." timeStamp="..." > dataType="..." label="..." responseCode="..." time="..." success="..."/> > > I only noticed this since I used Perl to parse the logfiles and my regex > broke. The obvious (and surprising) conclusion is that something changed in > Java's XML handling between 1.4.2_02 and 1.4.2_08 ! > > Regards, > Sonam Chauhan > -- > Electronic Commerce, Corporate Express Australia Ltd. > Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
