[JBoss-user] [JBoss Seam] - Re: SFSB are evil? (The eternal Update problem)

2006-06-23 Thread baz
anonymous wrote : BTW: Could you please be more specific where to look a the hotel booking | example. I meant the booking example for hibernate and tomcat. There exists in class HotelBookingAction this method: @End |public String clear() |{ | hotels = null; |

[JBoss-user] [JBoss Seam] - Re: SFSB are evil? (The eternal Update problem)

2006-06-22 Thread fhh
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

[JBoss-user] [JBoss Seam] - Re: SFSB are evil? (The eternal Update problem)

2006-06-22 Thread baz
Hello, Your problem looks very common for me. anonymous wrote : I checked it, and the find() method is not called when I revisit the page. That is correct. The find() method is only called when vertraege is null. That is the meaning of a factory method. anonymous wrote : How can I enforce that

[JBoss-user] [JBoss Seam] - Re: SFSB are evil? (The eternal Update problem)

2006-06-22 Thread dahm
Hi, thanks for the reply... anonymous wrote : | How can I enforce that the list is reread? | anonymous wrote : | Easy answer. You have to set vertraege to null. | But to implement it is sometimes not so easy. Look at the hotelbooking example for a hint. | It's not that easy