In that case I will be touching the source code of NHibernate and what would be the things required to do if we change NH source code
1. I would have release NH 1.2.1 with the patch ? 2. Does that make my app vulnerable to be part of open source as well according to LGPL? Thanks On May 4, 12:06 am, Tuna Toksoz <[email protected]> wrote: > You can do that too. Just slap [Serializable] on almost every problematic > thing would work. > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/tehlike > > On Sun, May 3, 2009 at 9:23 PM, codegoblin <[email protected]> wrote: > > > Hi Tuna > > > When you mean trunk does it mean its alpha version and cannot be used > > in production stable code? Also can I use any patch for NH 1.2.1 to > > make configuration serializable? > > > On May 1, 11:34 pm, Tuna Toksoz <[email protected]> wrote: > > > In 1.2.1? No, in 2.1 trunk? yes. > > > >http://nhforge.org/blogs/nhibernate/archive/2009/03/13/an-improvement... > > > > Tuna Toksöz > > > Eternal sunshine of the open source mind. > > >http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitt... > > > > On Fri, May 1, 2009 at 9:32 PM, codegoblin <[email protected]> wrote: > > > > Also Can I serialize my configuration object if yes how since its > > > > giving me exception while binary serializing it. DO i need to make any > > > > changes in NH code for this --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
