If GWT translated to an intermediate form, it would be so close to source-code that it really wouldn't matter.
Besides that, GWT compiles from source-code to source-code (although it's JavaScript source code). I've seldom worked with a commercial enterprise product that I can't get the source-code for, especially not an API product. I would say this is more a legal issue than one related to the way GWT (or any other compiler) does things. You could always obfuscate the Java source code before JARing it up, it offers about as much security as GWT does with it's Obfuscated JavaScript output. Just my 2c worth. //J Mike wrote: > Dear all, > > Is it possible to create a GWT-library that can be included in other > GWT projects *without* giving away the source code? > >>From what i understand, currently both the sources and the .class > files should be included in a library. Including the sources can be a > problem wrt intellectual property if the logic is nontrivial and of > substantial size. Why doesn't GWT translate into some intermediate > form, or just use javascript? > > Bye, Mike > > > > --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
