This content has been marked as final.
Show 4 replies
-
1. Re: ManagedObjectAttachmentsImpl::transientManagedObjects no
starksm64 Jul 21, 2008 12:30 AM (in response to alesj)Its transient in that it does not affect that persistent view of the metadata as known by the profile service.
-
2. Re: ManagedObjectAttachmentsImpl::transientManagedObjects no
adrian.brock Jul 21, 2008 6:25 AM (in response to alesj)No, its an error in the refactoring.
See transientAttachments here:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/microcontainer/tags/OLD_DEPLOYERS/deployers/src/main/org/jboss/deployers/plugins/structure/AbstractDeploymentContext.java?revision=64008&view=markup
Transient attachments should not be serialzied unlike transient managed objects. -
3. Re: ManagedObjectAttachmentsImpl::transientManagedObjects no
alesj Jul 21, 2008 1:13 PM (in response to alesj)"adrian@jboss.org" wrote:
Transient attachments should not be serialzied unlike transient managed objects.
I'm confused now. :-)
The old code had transientManagedObjects transient.
Current code doesn't.
What should be then? :-) -
4. Re: ManagedObjectAttachmentsImpl::transientManagedObjects no
starksm64 Jul 21, 2008 2:00 PM (in response to alesj)Both are logically transient and Adrian is saying they should be physically transient as well in terms of the default java serialization behavior. We used to have:
/** The attachments */ private transient Attachments transientAttachments = new AttachmentsImpl(); /** The managed objects */ private transient Attachments transientManagedObjects = GeneratedAOPProxyFactory.createProxy(new AttachmentsImpl(), Attachments.class);
Now transientAttachments exists as ManagedObjectsWithTransientAttachmentsImpl.transientAttachments and is marked transient, and transientManagedObjects exists as ManagedObjectAttachmentsImpl.transientManagedObjects and is not marked transient. Its also no longer an aop proxied instance.