different jdk behavior depending on OS or version

[Juergen Donnerstag <ju...@gmail.com>]

It was new to me, but may be you are already aware of it. I was using
jdk 1.6 to run the tests on my windows pc and all tests passed. I
recognized that Bamboo failed (and eelco fixed it)  but I couldn't
quite figure out why. Now I know. I changed jdk back to 1.4 and now it
works with eelco's changes. This means that jdk 1.6 has changed its
Map implementation (the iterator) and people must expect some tests to
fail if testing new jdk versions.

regards
Juergen


---------- Forwarded message ----------
From: ehillenius@apache.org <eh...@apache.org>
Date: Apr 30, 2007 11:11 AM
Subject: svn commit: r533637 -
/incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html
To: wicket-commits@incubator.apache.org


Author: ehillenius
Date: Mon Apr 30 02:11:55 2007
New Revision: 533637

URL: http://svn.apache.org/viewvc?view=rev&rev=533637
Log:
unit test fix

Modified:
    incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html

Modified: incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html
URL: http://svn.apache.org/viewvc/incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html?view=diff&rev=533637&r1=533636&r2=533637
==============================================================================
--- incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html
(original)
+++ incubator/wicket/trunk/jdk-1.4/wicket/src/test/java/org/apache/wicket/markup/html/basic/SimplePageExpectedResult_7.html
Mon Apr 30 02:11:55 2007
@@ -5,10 +5,10 @@
   <wicket:message key="myKeyNotExsts"/>
   <wicket:message key="myKey">myValue</wicket:message>
   <span wicket:id="message">here it goes</span>
-  <span wicket:message="attr-name:i18n-key" attr-name="my i18n
key">test 2</span>
-  <span wicket:message="attr-name:i18n-key" attr-name="my i18n key"
wicket:id="message2">here it goes</span>
+  <span attr-name="my i18n key"
wicket:message="attr-name:i18n-key">test 2</span>
+  <span wicket:id="message2" attr-name="my i18n key"
wicket:message="attr-name:i18n-key">here it goes</span>

-  <input src="/WicketTester$DummyWebApplication/test.gif"
type="image">test 2</input>
-  <input wicket:message="attr-name:i18n-key" attr-name="my i18n key"
src="/WicketTester$DummyWebApplication/test.gif" type="image">test
2</input>
+  <input type="image"
src="/WicketTester$DummyWebApplication/test.gif">test 2</input>
+  <input type="image"
src="/WicketTester$DummyWebApplication/test.gif" attr-name="my i18n
key" wicket:message="attr-name:i18n-key">test 2</input>
 </body>
 </html>

Re: different jdk behavior depending on OS or version

[Johan Compagner <jc...@gmail.com>]

didn't jonathan work on that already?
that he did a diff with our xml parser??

johan


On 5/1/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > It was new to me, but may be you are already aware of it. I was using
> > jdk 1.6 to run the tests on my windows pc and all tests passed. I
> > recognized that Bamboo failed (and eelco fixed it)  but I couldn't
> > quite figure out why. Now I know. I changed jdk back to 1.4 and now it
> > works with eelco's changes. This means that jdk 1.6 has changed its
> > Map implementation (the iterator) and people must expect some tests to
> > fail if testing new jdk versions.
>
> Yeah, Jonathan had the exact same problems. It would be great if we
> could find a reasonable solution for this, as it's our testing that is
> brittle really, but it looks like it might be either hack-ish or
> difficult depending on how well we want to solve it. You have any
> ideas Juergen?
>
> Eelco
>

Re: different jdk behavior depending on OS or version

[Eelco Hillenius <ee...@gmail.com>]

> It was new to me, but may be you are already aware of it. I was using
> jdk 1.6 to run the tests on my windows pc and all tests passed. I
> recognized that Bamboo failed (and eelco fixed it)  but I couldn't
> quite figure out why. Now I know. I changed jdk back to 1.4 and now it
> works with eelco's changes. This means that jdk 1.6 has changed its
> Map implementation (the iterator) and people must expect some tests to
> fail if testing new jdk versions.

Yeah, Jonathan had the exact same problems. It would be great if we
could find a reasonable solution for this, as it's our testing that is
brittle really, but it looks like it might be either hack-ish or
difficult depending on how well we want to solve it. You have any
ideas Juergen?

Eelco