injected EntityManager in EJBs and POJOs

[robshep]

If I have a @Stateful session bean,

then a merge(entity); flush(); permits me to either persist or update a new or detached entity.

If I turn the bean in to a regular POJO seam component, then it doesn't persist the entity.

Can anybody explain why?

In a @Stateful EJB, is a @In EntityManager SEAM or Container managed?

Thanks

Rob

[phantasmo]

@In EntityManager always injects the Seam managed persistence context, as @In obviously injects Seam's components.
Now, I have no clue why would merge() behave differently under differently injected entity managers... What happens when you invoke it from a JavaBean component?

[jeanluc]

turn on Hibernate tracing and check if no SQL statements are issued or, perhaps, they are issued but the transaction is not committed. At least you reduce the search space.