Hi,
We use an entity bean that contains a attribute of type java.util.Set.
This bean has the following methods for this attribute:
@OneToMany(fetch = FetchType.LAZY, mappedBy = parent)
public Set getChilds() {
return childs;
}
public void
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
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
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 :
Hi,
We have JBoss AS 5.1.0 and use hibernate to store our session beans in MySQL
DB. Also pojo caching is used to make the objects available throughout the
cluster.
For both hibernate and caching we use annotations.
@Replicable for classes that need to go into cache and
@Entity for objects
