OK, I guess I solved my problem. This is what I ended up doing:
| KidBean kid = parent.getKids().get(mappingIndex); | em.remove(kid); | parent.getKids().remove(mappingIndex); | em.merge(parent); | return parent; | Seems if I don't return the parent changes aren't made evident in the front end and that detached bean ends up updating the database somehow. I didn't think that was possible. Anyway, by ensuring that the merge happens in the session bean and returning it to the front end things work. Thanks for everyone that looked and thanks again, Chris. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3954036#3954036 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3954036 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
