I don't know why you need to recreate the session-factory so often, IMO there is something wrong in somewhere else or NH is not the project for your needs.
2009/6/29 Mind Works <[email protected]> > > Thanks Fabio. > > e.g. We have 10 objects and we build a session factory. Now when 11th > object comes we destroy the existing session factory and create a new > one with 11 objects. Now this session factory is being assigned to > ISession.SessionFactory (by changing code to add new setter property). > So Session will be aware of who created it?? > > Thanks & Regards, > > On Jun 29, 11:07 pm, Fabio Maulo <[email protected]> wrote: > > 2009/6/29 Mind Works <[email protected]> > > > > > 1. Is the above change to NH a valid change. > > > > No. > > The session-factory, as its name mean, is the factory of session that > mean a > > session can know who have created it and you can't change the creator (as > > everybody can't change his natural mother). > > > > > > > > > 2. What is the procedure to follow such that the above change can be > > > published. - I am aware that NH is under LGPL license, and we wish to > > > distribute the changes as part of our deployment. > > > > Ask to your lawyer to read with attention the LGPL license. > > > > -- > > Fabio Maulo > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
