Sorry Poorna, I have not completely looked through the patch. I'll try to review it later today. A new callback onDestroy(request, session) sounds reasonable. We definitely need to make sure these changes are backward compatible. I do not know of any way to create control container context without requiring a request.
Kind regards, Carlin On 12/19/07, Poorna Ramasamy <[EMAIL PROTECTED]> wrote: > Did anyone get a change to look at this? > > regards, > ~Poorna > > > > -----Original Message----- > From: Poorna Ramasamy > Sent: Wednesday, December 12, 2007 10:24 PM > To: Beehive Developers > Cc: Carlin Rogers > Subject: RE: BEEHIVE-1094 > > Attached diff is the new solution I have in my mind now. That is, > request is being tracked right from where the pageflow is removed from > session using the SessionBindingEvent. At the destroy method if request > is available, context is created or else onDestroy(session) is called > without context. > > But I feel, with this approach, customers would not be certain about the > context being associated with onDestroy(session). If session > invalidation occurs, onDestroy(session) will be called without context. > So to overcome this, I feel, a new callback onDestroy(request, session) > is required here. Does this sound reasonable? Or if there is a way in > which I can create control container context without requiring "request" > object, please let me know. > > regards, > ~Poorna > > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. >
