I found following commit in svn:
Resolves OGNL-49. Was getting compilation errors from javassist in disabled
caching mode because sometimes the hashcodes were equal for class
names...Added a global increment counter to force uniqueness.
Without globalCounter code works perfectly on WebSphere.
P
2007/5/16, Alex Rytov <[EMAIL PROTECTED]>:
Sorry, as i see the problem in Tapestry 4.1.2-SNAPSHOT.
Tapestry 4.1.1 works with javassist 3.4 and
ognl-2.7-20070425.021856-29.jar
correctly.
Yes. Tapestry-4.1.1 works fine with javassist-3.4 and
ognl-2.7-20070425.021856-29.jar.
There must be somet
Sorry, as i see the problem in Tapestry 4.1.2-SNAPSHOT.
Tapestry 4.1.1 works with javassist 3.4 and ognl-2.7-20070425.021856-29.jar
correctly.
Alex Rytov wrote:
>
> There is something wrong with IBM JVM (1.5.0) and javassist version (3.3,
> 3.4, 3.5-SNAPSHOT)
> Previous version of Tapestry (4.1
There is something wrong with IBM JVM (1.5.0) and javassist version (3.3,
3.4, 3.5-SNAPSHOT)
Previous version of Tapestry (4.1.1) runs correctly (cause javassist version
3.0)
[5/16/07 10:48:08:143 MSD] 0022 HiveMindExpre E
org.apache.tapestry.services.impl.HiveMindExpressionCompiler
compileEx
Maybe websphere is causing some other version of javassist to be used?
On 5/15/07, Denis Burlaka <[EMAIL PROTECTED]> wrote:
Hi.
I attempted to run my application on the IBM WebSphere 6.1.0.7, but the
next
exception occurres:
[15.05.07 13:38:28:812 MSD] 001e SystemErr R
org.apache.hive
