Thanks Gordon! I'll forward your response to the submitter.
Gordon Yorke wrote:
>Hello Amy, here is my responce:
>
>First, yes the TopLink Agent can be used within an App Server when JSE based behaviour is being used.
>Second, I am not sure how you were lead to beleive that TopLink would fetch 'lazy' loaded attributes of serialized object but once an object has been serialized those lazy attributes are detatched and can not be fetched by TopLink. There are no planned features to provide 'reconnection' of serialized lazy attributes.
>Perhaps if you could explain what you are attempting and what behaviour this lifecycle module is emulating some alternatives could be suggested?
>--Gordon
>
>-----Original Message-----
>From: Amy Roh [mailto:Amelia.Roh_at_Sun.COM]
>Sent: Thursday, November 17, 2005 12:50 PM
>To: persistence_at_glassfish.dev.java.net
>Subject: Re: Two More Ask the Expert Questions
>
>
>Can someone answer this question?
>
>
>
>>question: Hello! Basically, I'd like to use lazy CMR from a lifecycle
>>module.
>>
>>Q: Will the TopLink-agent work in the same JVM with appserver?
>>
>>Alternate Question: Is there another approach for the case?
>>Apparently, the TopLink
>>RemoteSessions won't be included/supported? The component wrapped
>>inside a lifecycle module
>>is not suitable for SB-wrapping, but I wouldn't like to take it out of
>>the server either.
>>
>>Additional Description: While fetching an EB from a remote
>>facade-slessbean, the TopLink-agent
>>should apparently manage the deferred (access-time) loading of
>>referenced EBs by instantiating
>>a local EntityManagerFactory (i.e., the whole persistency module) for
>>the lifecycle module. However, this doesn't seem to work currently
>>(which can still be well understood.)
>>As a temporary work-around, I'm circumventing the use of SBs and
>>instantiating the EntityManager
>>"manually" within the lifecycle module.
>>
>>
>
>Thanks!
>Amy
>
>
>