As you mentioned in your previous mail, you are not a lawyer. So you can come with theories and interpretations of LGPL and decide on use of a library. I suspect you are a happy user of GWT and the widgets it provides out of the box and that if you really wanted to use SmartGWT LGPL, you'd consult the legal team of your company rather than speculation based on your "non lawyer" interpretation of what really is pretty clearly spelled out in the SmartGWT license file COPYING.html.
FYI Hibernate also adds the clarification on what they consider dynamic linking and that use of Hibernate never affects the license of the users code. https://www.hibernate.org/356.html The SmartGWT license clarification was based on this. The use of Hibernate is also not without caveats as you make it sound. Any application that users Hibernate also runs into a gray area since due to dynamic proxying of objects by Hibernate there is indeed modification involved. This is the very reason that Hibernate too added the above license clarification. If you are a user of Spring, Spring has a class IdTransferringMergeEventListener that extends org.hibernate.event.def.DefaultMergeEventListener and modifies its runtime behavior. Nobody is forcing anyone to use a free product - SmartGWT LGPL, and similarly no favors are being done if anyone does chose to use the free product. This is getting off topic now. If anyone needs further LGPL clarifications when using SmartGWT, feel free to post on the SmartGWT forum. Sanjiv On Thu, Jan 14, 2010 at 4:04 AM, Paul Robinson <ukcue...@gmail.com> wrote: > Sanjiv Jivan wrote: > > SmartGWT has had the same clause since for a long time now. Read the > > actual license file - COPYING.html that is included in the SmartGWT > > distribution. > > > > > http://code.google.com/p/smartgwt/source/browse/trunk/distro-source/core/src/COPYING.html > You're right. SmartGWT has modified/clarified their use of the LGPL > specifically to cover this point. > > It's worth noting that the widely used Hibernate library is also > > licensed under LGPL terms. > Yes, but Hibernate lives only on the server side, so doesn't suffer the > same problem. The GWT-LGPL issue is strictly a client-side problem and > this is why I'm happy to use Hibernate in my server code. > > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
