18 Dec
2009
18 Dec
'09
4:42 p.m.
On 12/18/2009 01:36 PM, Reto Hotz wrote:
Hi,
FYI: We have experienced problems running XWiki 2.1 on Glassfish 2.1.1
(see stacktrace at the end).
Our final solution was to replace the bundled cglib-2.1_3.jar with the
newest cglib-2.2.jar
So the solution is to also update it in the default distribution, right?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
19 Dec
19 Dec
2:49 a.m.
New subject: [xwiki-devs] [xwiki-users] XWiki + Glassfish 2.1.1 + cglib
On 12/18/2009 04:42 PM, Sergiu Dumitriu wrote:
On 12/18/2009 01:36 PM, Reto Hotz wrote:
It seems that cglib-2.2 uses asm-3.1, while Hibernate still uses
asm-1.5.3, and I don't know if those two are compatible. Are you sure
the wiki runs without any problems? Can you also try replacing the
asm-1.5.3.jar file with this one:
http://repo2.maven.org/maven2/asm/asm/3.1/asm-3.1.jar
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
FYI: We have experienced problems running XWiki 2.1 on Glassfish 2.1.1
(see stacktrace at the end).
Our final solution was to replace the bundled cglib-2.1_3.jar with the
newest cglib-2.2.jar
So the solution is to also update it in the default distribution, right? 
21 Dec
21 Dec
8:53 a.m.
New subject: [xwiki-devs] [xwiki-users] XWiki + Glassfish 2.1.1 + cglib
Hi,
On 19.12.2009 02:49, Sergiu Dumitriu wrote:
On 12/18/2009 04:42 PM, Sergiu Dumitriu wrote:
I have now also updated asm 1.5.3 to asm-3.1 and everything seems to
work fine. No strange behaviors, no exceptions in the log.
So for me, yes the solution would be to update cglib (and probably also
asm) to the newer version in the default distribution.
Greetings
Reto
On 12/18/2009 01:36 PM, Reto Hotz wrote:
It seems that cglib-2.2 uses asm-3.1, while Hibernate still uses
asm-1.5.3, and I don't know if those two are compatible. Are you sure
the wiki runs without any problems? Can you also try replacing the
asm-1.5.3.jar file with this one:
http://repo2.maven.org/maven2/asm/asm/3.1/asm-3.1.jar Hi,
FYI: We have experienced problems running XWiki 2.1 on Glassfish 2.1.1
(see stacktrace at the end).
Our final solution was to replace the bundled cglib-2.1_3.jar with the
newest cglib-2.2.jar
So the solution is to also update it in the default distribution, right?
5383
days inactive
5386
days old
2 comments
2 participants
participants (2)
-
Reto Hotz -
Sergiu Dumitriu