[JBoss JIRA] Created: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
6:03 p.m.
ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
--------------------------------------------------------------------------------
Key: JBSEAM-4589
URL: https://jira.jboss.org/jira/browse/JBSEAM-4589
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.2.GA
Reporter: Sebastien Boutte
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:36 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
[
https://jira.jboss.org/jira/browse/JBSEAM-4589?page=com.atlassian.jira.pl...
]
Sebastien Boutte commented on JBSEAM-4589:
------------------------------------------
Hope it's a good correction ;)
ManagedEntityWrapper wrap and deserialize with in-depth fields of
Stateful Beans
--------------------------------------------------------------------------------
Key: JBSEAM-4589
URL: https://jira.jboss.org/jira/browse/JBSEAM-4589
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.2.GA
Reporter: Sebastien Boutte
Attachments: 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
[
https://issues.jboss.org/browse/JBSEAM-4589?page=com.atlassian.jira.plugi...
]
Peter Brewer commented on JBSEAM-4589:
--------------------------------------
I've tested this patch on my local environment and it fails to restore the entities
properly. Also, I think the algorithm may be quite intensive as it recurses through the
entire object hierarchy of each field in the bean.
However, I'm going to take the patch as a starting point and I'm currently
investigating a fix for this. I'll let you know how I get on.
ManagedEntityWrapper wrap and deserialize with in-depth fields of
Stateful Beans
--------------------------------------------------------------------------------
Key: JBSEAM-4589
URL: https://issues.jboss.org/browse/JBSEAM-4589
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.2.GA
Reporter: Sebastien Boutte
Attachments: 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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Updated: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
[
https://issues.jboss.org/browse/JBSEAM-4589?page=com.atlassian.jira.plugi...
]
Peter Brewer updated JBSEAM-4589:
---------------------------------
Attachment: JBSEAM-4375 and JBSEAM-4589.diff
Patch also incorporates the changes in JBSEAM-4375
ManagedEntityWrapper wrap and deserialize with in-depth fields of
Stateful Beans
--------------------------------------------------------------------------------
Key: JBSEAM-4589
URL: https://issues.jboss.org/browse/JBSEAM-4589
Project: Seam
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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:41 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans
[
https://issues.jboss.org/browse/JBSEAM-4589?page=com.atlassian.jira.plugi...
]
Peter Brewer commented on JBSEAM-4589:
--------------------------------------
I've applied a patch that I have up and working on my local environment.
The patch will now save entities to the conversation even if they are wrapped or embedded
in a complex user defined data-structure. However, for the sake of performance such
wrapped entities must be annotated on the field with
org.jboss.seam.annotations.persistence.EntityWrapper. This is a marker interface that
tells the ManagedEntityWrapper to drop into wrapper and then perform passivation at that
level. Further entity wrappers down the object graph must also be annotated though.
There are a couple of issues so far:
1. Recursive references are not handled, I'm currently working on this(should be quite
simple), but thought others may like the patch straight away.
2. The field reference is not set to null, so the entity is serialized twice, once in the
field and once in the conversation. This is so that the deserialization process has
knowledge of the runtime type of the field, but it may be possible to fix this.
3. If a Collection or Map is annotated with EntityWrapper it must provide guaranteed
ordering otherwise activation may break. Not sure how to avoid this, so suggestions
welcome.
Please let me have any feedback you may have.
ManagedEntityWrapper wrap and deserialize with in-depth fields of
Stateful Beans
--------------------------------------------------------------------------------
Key: JBSEAM-4589
URL: https://issues.jboss.org/browse/JBSEAM-4589
Project: Seam
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 is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5107
days inactive
5417
days old
4 comments
2 participants
participants (2)
-
Peter Brewer (JIRA) -
Sebastien Boutte (JIRA)