Why @ViewScope and Seam Managed Persistence Context doesn't work?

[rafaelmeireles]

Hello friends,

How I use Seam Managed Persistence Context with @ViewScope? When I put:

@SuppressWarnings("unused")

@ExtensionManaged

@Produces

@PersistenceUnit

@ViewScope

private EntityManagerFactory entityManagerFactory;

This messege is showed: The annotation @ViewScoped is disallowed for this location

So for test I use:

@SuppressWarnings("unused")

@ExtensionManaged

@Produces

@PersistenceUnit

@ConversationScope

private EntityManagerFactory entityManagerFactory;

And my JSF Managed Bean:

@Named

@ViewScoped

public class ClienteAction implements Serializable

The EntityManager created by the seam is an EntityManager managed, it show like this: EntityManager$ManagedPersistenceContext$1828725225$Proxy$_$$_WeldClientProxy  (id=155)

But when I test if an Entity is managed(entityManager.contains(entity)) the entity is managed only in the first ajax request, I think as, for each request a new conversation is created, therefore in the first ajax request the entity is managed by the entityManager.

[zeeman]

I have the same exact problem that has been driving me crazy. Any ideas?

Also, Seam managed EM on a stateless EJB does not work either. I get get conversation context is inactive. I tried with OP listed above to produce an EM with a different scope but it still does not work. What are we missing?

[rafaelmeireles]

The seam 3 apparently does not work fine with ViewScope. I was disappointed with seam 3. Known issues are still unresolved.

[rafaelmeireles]

zeeman, do you solved this problem? Anybody can help?

[zeeman]

No solution. I was hoping to find one here.

[romanow]

I saw similar behavior on my pages. It was always JPA issue. Entity is taken from DB, displayed on the page, updated to DB and on second AJAX call entity is not in EM.  This is actually a good thing when you think about it.

Your case may be different. Try conversation or session scope to verify my theory.

ViewScope works pretty nice for me.

I experienced some issue with conversation. There are big differences between Seam 2 and Seam 3, you may want to read about it. Also I found that explicit propagation of conversation works better than annotated. In my case that was when I tried to propagate from PostConstruct.

[rafaelmeireles]

With conversation it work, but the advantage of ViewScope is that I don't explicit begin or end nothing. Nobody of seam team that can help?

I think in this integration with jsf 2 Spring it is more mature than seam.

[hantsy]

I encountered some problems before when I used @ViewScoped in the Seam 3.x

So I used ConvesationScoped as posible.

And some other scope, application, request, session, never used @ViewScoped.

[rafaelmeireles]

This problem is in seam-faces module? If I will create an issue to solve the problem.

[zeeman]

Please keep this thread updated with JIRA issue and solution.

[rafaelmeireles]

This solution works fine for me:

http://www.verborgh.be/articles/2010/01/06/porting-the-viewscoped-jsf-annotation-to-cdi/

any doubt ask me.

[zeeman]

Rafael,

I don't see how is the solution in provided link for implementing a @Viewscope would help with injecting an EntityManager?

Can you explaing how would that solution help with the problem in OP's thread? Thanks.

[hantsy]

it is rewritten in CDI instead...

I think all JSF scopes should be mapped to CDI compitable Scopes and will make thing simple.

Have a look at the MyFaces CODI, a subproject of Apache MyFaces.

[rafaelmeireles]

zeeman wrote:

Rafael,

I don't see how is the solution in provided link for implementing a @Viewscope would help with injecting an EntityManager?

Can you explaing how would that solution help with the problem in OP's thread? Thanks.

Follow this article the entity pass to be managed between request, because in this article the author overwrite the annotation @ViewScope so the annotattion can be used like this:

@SuppressWarnings("unused")

@ExtensionManaged

@Produces

@PersistenceUnit

@ViewScope

private EntityManagerFactory entityManagerFactory;

[anadollu]

Try this solution:

https://community.jboss.org/message/652514#652514