[jboss-user] [JNDI/Naming/Network] - Re: When deploying stateful session bean, it shows via JNDI

Hi, I'm experiencing the same problem as described in the original post. I've read the information within the link regarding ClassCastExceptions but cannot resolve the issue. My EAR file is being packaged via Eclipse (Ganymede) and the Bean itself resides within a JAR at top level described w

[jboss-user] [EJB 3.0] - MappedSuperClass propogation through multiple inheritance le

Hi, I'm using JBOSS 4.2.2 and developing with Eclipse Ganymede against MySQL. I've created several entity beans inheriting from an abstract class annotated with @MappedSuperclass. This class (a) contains four columns, annotated appropriately, common to both beans below it for optimistic lockin

[jboss-user] [EJB 3.0] - Optimistic locks and detached(?) entities

Hi, I'm working on an EJB3 application using a JSP/Servlet front end on JBoss 4.2.2 GA against MySQL. As part of a web based application process I'm persisting an entity within a session bean method. I then call flush() and refresh() on the entity manager so that the last modified and version

[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - OptimisticLockException thrown on entity manager merge(). Wh

Hi, I posted this earlier in the EJB3 form, but realise now that this is probably a more appropriate place for it. Apologies for the multiple posts! I'm working on an EJB3 application using a JSP/Servlet front end on JBoss 4.2.2 GA against MySQL. As part of a web based application process I

[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: OptimisticLockException thrown on entity manager merge()

Hi, Many apologies, problem solved. I had another process updating the entity and therefore incrementing the version number, so receiving the exception was the expected behaviour after all. All fixed now and merging as expected. Many thanks Alistair View the original post : http://www.j

[jboss-user] [EJB 3.0] - Re: Optimistic locks and detached(?) entities

Hi all, Many apologies, problem solved. I had another process updating the entity and therefore incrementing the version number, so receiving the exception was the expected behaviour after all. All fixed now and merging as expected. Many thanks Alistair View the original post : http://www