you're client is using a new session bean for each lap. try changing it to:
... // lap 2 peliculas = proceso.listarPeliculas(); showPeliculas(peliculas); proceso.grabar(); System.out.println("Lap 2 OK!");
each time you do a lookup for a stateful bean you'll get a new one.
waynebaylor: that for you help!
But see my method grabar(), this is annotated with @Remove, for flush every modification, then the original bean is detroyed and I need new one.
The SFSB make the work of keep a conversation (like seam do).
i think the @Remove annotation means that it will be called when the bean is removed from the pool, not that the bean will be removed with it's called.
ummm... @Remove not is a callback method, like PreDestroy, etc.
@Remove is the only one called by code, not by container.
Thanks any way,