Well, this is how stateful session beans are supposed to work. They save their state and that includes your List _vertraege.
So the question is what you really want to do. If you want to keep in sync with the database at any cost, you could user a stateless session bean. But doing so will cost performance since the db is re-read for every request. (I'm not sure how much is cached by hibernate. You may run into problems with hibernate cache) If you don't have a lot of use (and not too man vertraege in the db) the performance loss should be negligible. The "Big" solution would be to use JBoss' entity cache or implement your own caching strategy. But this will only work as expected iff your webapp is the ONLY application modifying the data in the db. Refards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952577#3952577 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952577 All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
