btw, im not actually suggesting you do that because keeping the key
pieces in memory must be a lot faster than pulling from the DB for
every component

On Wed, Oct 7, 2009 at 7:34 PM, Marcelo Fukushima <[email protected]> wrote:
> cant you inject the DAO's to the listeners in the moment you create
> and attack the listeners to your application?
> If you have the Injector at that moment, you could even pull your
> listeners from the Injector, no?
>
> On Wed, Oct 7, 2009 at 5:21 PM, Jeffrey Schneller
> <[email protected]> wrote:
>> Thanks.  I took your suggestion and now just store the key pieces that I 
>> need in the session and it looks like it is working.
>>
>> -----Original Message-----
>> From: Martin Makundi [mailto:[email protected]]
>> Sent: Wednesday, October 07, 2009 1:05 PM
>> To: [email protected]
>> Subject: Re: Storing entity object in session - how to do it?
>>
>> We have (some key) entities (successfully) in Session. But they are
>> not lazy-load entities so they act like plain-old-java-beans.
>>
>> **
>> Martin
>>
>> 2009/10/7 Jeffrey Schneller <[email protected]>:
>>> Looking through the archives I saw some posts that said you should not
>>> store entity objects [for example object coming from hibernate] in the
>>> session.  This makes sense to me as I just hit the problem.
>>>
>>> The archives gave lots of advice but everything seemed to contradict and
>>> no one posted a working solution.
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
>
> --
> http://mapsdev.blogspot.com/
> Marcelo Takeshi Fukushima
>



-- 
http://mapsdev.blogspot.com/
Marcelo Takeshi Fukushima

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to