Problems using Extended Persistence Context

[daniel.celentano]

I'm using EXTENDED Persistence Context with a SFSB, expecting that "the lifecycle of the persistence context is binded to the lifecycle of the Stateful Session Bean" but this dont work.

I'm get org.hibernate.LazyInitializationException in the second lap, this is the same method invocation with different results. May by a Bug?

This is my code:

CLIENT

public class Client
{
public static void main(String[] args) throws Exception
{
InitialContext ctx = new InitialContext();
IProceso proceso = (IProceso) ctx.lookup("cine/ProcesoBean/remote");
List peliculas = null;


// lap 1

proceso.crearDatos();
peliculas = proceso.listarPeliculas();
showPeliculas(peliculas);
proceso.grabar();
System.out.println("Lap 1 OK!");

// lap 2
proceso = (IProceso) ctx.lookup("cine/ProcesoBean/remote");
peliculas = proceso.listarPeliculas();
showPeliculas(peliculas);
proceso.grabar();
System.out.println("Lap 2 OK!");

}


SERVER


@Stateful
public class ProcesoBean implements IProceso{

@PersistenceContext(type=PersistenceContextType.EXTENDED)
private EntityManager em;


public void crearDatos(){
System.out.println("crearDatos");
System.out.println("EM: " + em.hashCode());
// make data insert on DB

....


@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public List listarPeliculas() {

List pelis = null;
pelis = em.createQuery("from Movie p where p.salaCompleta is false").getResultList();
return pelis;
}



@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public void salaCompleta(Long idpelicula) {
Movie pelicula = em.find(Movie.class, idpelicula);
pelicula.setSalaCompleta(Boolean.TRUE);
}


@Remove
public void grabar() {
}

[waynebaylor]

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.

[daniel.celentano]

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).

[waynebaylor]

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.

[daniel.celentano]

ummm... @Remove not is a callback method, like PreDestroy, etc.
@Remove is the only one called by code, not by container.

Thanks any way,
Daniel