I upgraded our organization to 3.12.0.GA javassist and a lot of issues
went away. Still a few issues, and I think the guy who patched it for
us submitted that patch to javassist, but it's light-years less
problematic than 3.9.
Christian
On Jul 9, 2010, at 5:37 AM, Halil Karakose wrote:
A
After a jboss restart and clean deploy, the application is deployed fine.
Below is what I did:
- javassist.jar is removed from JBOSS_HOME/server/default/lib folder.
- javassist-3.9.0-GA.jar is put inside JBOSS_HOME/server/default/lib
folder.
- javassist-3.9.0-GA.jar is removed from WEB
Actually this is the default Appfuse User class. And the class has no-arg
constructor.
I've been debuggin jboss now. During jboss startup,
javassist.util.proxy.ProxyFactory.setField() method throws the exception in
the following highlighted line.
private void setField(String fieldName
Make sure com.mycompany.model.User has non-args public constructor.
On Thu, Jul 8, 2010 at 12:49, Halil Karakose wrote:
> Changing javassist jar didn't work. I still receive the errors.
>
> By the way, the exception is thrown by
> "org.hibernate.tuple.entity.PojoEntityTuplizer".
> Is there a inco
Changing javassist jar didn't work. I still receive the errors.
By the way, the exception is thrown by
"org.hibernate.tuple.entity.PojoEntityTuplizer".
Is there a incompatibility with the hibernate jars?
One more issue is that the logging level of the stack trace is in WARN
level. And I still hav
I think you should update the javassist in jboss/server/default/lib/ folder.
Joachim
On 07/01/2010 08:08 AM, Halil Karakose wrote:
Hi,
I receive an error in my Tapestry webapp. I use Tapestry 5.1.0.5 and Jboss
4.2.3-GA.
*Scenario 1:*
My web application contains javassist 3.9.0.GA in WEB-INF/l
Hi,
I receive an error in my Tapestry webapp. I use Tapestry 5.1.0.5 and Jboss
4.2.3-GA.
*Scenario 1:*
My web application contains javassist 3.9.0.GA in WEB-INF/lib folder. And
there is also another javassist.jar(3.6.0.GA) file inside
jboss/server/default/lib folder.
During deployment of the web