I'm tinkering with seam persistence (Beta1). The documentation is a little light on how to set the flush mode to manual. I tried using a managed bean (@Named, not @ManagedBean) but after calling a method from my JSF page using ajax the transaction is flushed causing validation errors.

The documentation just stops with TODO: The next section needs to be updated to seam 3. and has copied verbatim from the seam 2 manual.

Also, if it hasn't been considered perhaps the default behavior could be manual flush. Would it be appropriate to set this as an attribute of @SeamManaged(flushMode=FlushModeType.MANUAL)? Of course this could be over-ridden on each bean.

When combining EJB session beans and CDI managed beans should the session bean @Inject the seam managed entityManager or use the @PersistenceContext annotation?

When injecting the seam managed entityManager into beans other the @ConversationScoped such as @RequestScoped what are the implications given that the seam managed provider is scoped as @ConversationScoped as in the following code:

@SeamManaged
@Produces 
@PersistenceUnit 
@ConversationScoped
EntityManagerFactory entityManagerFactory;