Frederic a écrit :
> Fabio Maulo a écrit :
>   
>> Are you sure that you are working with a single session instance ?
>> I guess that nobody in Spring's team can implement something like that.
>>
>> 2009/2/16 Frederic <f.ba <http://f.ba>@free.fr <http://free.fr>>
>>
>>
>>     Fabio Maulo a écrit :
>>     > 2009/2/16 Frederic <f.ba <http://f.ba> <http://f.ba>@free.fr
>>     <http://free.fr> <http://free.fr>>
>>     >
>>     >
>>     >     For the session, I've used a singleton, exposing a session
>>     through
>>     >     spring (handling callback and transaction).
>>     >
>>     >
>>     >
>>     >
>>     >     My big problem indeed, is that I'm thinking that what I
>>     would need
>>     >     is :
>>     >     - Disable the identity hashmap of the session (stateless
>>     session ?)
>>     >     - Rely on a global (factory ?) identity factory ?
>>     >
>>     >
>>     >
>>     > I don't understand exactly how you are managing the session, but
>>     > something in what you said sound as a time bomb.
>>     > --
>>     > Fabio Maulo
>>     >
>>     > >
>>     What exactly ?
>>
>>     I've used the spring nhibernate session management to expose a single
>>     session for one application server.
>>     For one service, we can use a specific transaction on the transaction.
>>
>>     Fred.
>>
>>
>>
>>
>>
>>
>>
>> -- 
>> Fabio Maulo
>>
>>     
> why ?
>
>
>
> >
>
>
>
>   
I'm using the NHibernate template.




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to