[jboss-user] [Clustering/JBoss] - Re: Caching, hybernate and using enums = no go
Could you please create a bug report in https://jira.jboss.org/jira/browse/JASSIST including the the code and full stacktrace that you got you encountered? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4244596#4244596 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244596 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Caching, hybernate and using enums = no go
Hi, filed this as a bug (JASSIST-90). regards, Werner van Mook View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4244652#4244652 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244652 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Caching, hybernate and using enums = no go
I have a solution for my problem. I replaced the switch statement in the Request class with an if() else statement. I am now able to deploy the application. Let this be a lesson for all: Do not use enum with javassist and switch statements together! Although if() else isn't beautiful programming it does the job and that's the most important thing! Thanks all that replied to my posting. Regards, Werner View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4243642#4243642 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243642 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Caching, hybernate and using enums = no go
If you want an Entity to be cached, I'd suggest you avoid @Replicable and instead configure it with @Cache annotation (see Hibernate/JPA annotations) so that the entity is added to the 2nd level cache. The 2nd level cache use case has been more road tested than what you're trying to do. See http://www.jboss.org/community/wiki/ClusteredJPAHibernateSecondLevelCachinginJBossAS5 for more info. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4243575#4243575 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243575 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Re: Caching, hybernate and using enums = no go
Well, This is exactly the problem. The object needs to be a entity hence the @entity annotation AND it needs to be in JBoss Cache. Don't ask why. It needs to be. In the meantime I figured out that the problem has to do with javassist. Something is going wrong there. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4243581#4243581 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4243581 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
