There's definitely something "interesting" going on somewhere. We're using
the Sun JDK 1.6 I downloaded several weeks ago. I honestly didn't spend a
lot of time isolating the issue, as since we're on JDK 1.6, I could just
eliminate the backport library entirely.
I can say I was getting the exac
That's weird, I use jdk6 on linux to develop Tapestry and haven't had any
issues.
Is this some kind of blackdown jre or ?
On 4/20/07, Jon McCarty <[EMAIL PROTECTED]> wrote:
I had this problem when running against JDK 1.6 on the Linux platform
(though
it worked on windows JDK 1.6 I think). It
I had this problem when running against JDK 1.6 on the Linux platform (though
it worked on windows JDK 1.6 I think). It may be that the
backport-concurrent library is not compatible with Linux JDK 1.6.
In order to fix this, I went ahead and took out backport-concurrent on our
local Tapestry 4.1.
