The problem I have is that the parent conversation has an object
(selectedDocument) which almost always gets updated by the nested action. If I
were to use a 'per-action' state is there any simple way of updating the object
in the parent conversation?
I would prefer to keep using the SMPC as it makes my code so much cleaner :)
The only significant amount of stale data would come from old
selectedDocument's, is there any way to manually evict them?
on a side note, what is the recommended way for recovering from a transaction
roll-back, At the moment I have lots of:
if (!em.contains(entity))
| entity = em.find(Entity.class, entity.getId)
scattered around, which does not seem to be the most elegant solution.
I have tried outjecting the id's and then reloading them in @Create and having
an ErrorHandler which does:
| ejbContext.setRollBackOnly();
| Contexts.removeFromAllContexts("seamComp")
but it doesn't seam to work as expected. Will the transaction always rollback
before the next render phase?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060997#4060997
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060997
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
