[seam-issues] [JBoss JIRA] (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans

[Ricardo Bento (JIRA)]

    [ https://issues.jboss.org/browse/JBSEAM-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073567#comment-13073567 ] 

Ricardo Bento commented on JBSEAM-4589:
---------------------------------------

I had a problem when i removed the entity that was loaded in parent conversation and I removed the entity in nested conversation, when it returned to parent it throwed an entityNotfound, with this patch It resolved. 

Could you attach the full source of the patch? It tried to reconstruct from the original and I would like to make sure that i got it rigth.

I now this is old but we cannot change versions ...

> ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
> --------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4589
>                 URL: https://issues.jboss.org/browse/JBSEAM-4589
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.GA
>            Reporter: Sebastien Boutte
>         Attachments: JBSEAM-4375 and JBSEAM-4589.diff, ManagedEntityWrapper.diff
>
>
> As it is said in documentation (Part : EJB Passivation and the ManagedEntityInterceptor) ; seam is capable of passivate SMPC (EntityManager with @In) and reattach all instances loaded at activation.
> For simple fields (Entities, Lists, Maps ...) , it works perfectly.
> For user defined fields (Wrapper with entity object, or more complex structure), this is not the case and cause a lazy exception later after activation.
> In class ManagedEntityWrapper, methods wrap and deserialize are not able to do in depth operations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)