This seems like a rather complex way to go about it. It seems like it would be simpler to do it the usual Java way of programming against interfaces and then using deferred binding to set which class actually gets used. Of course if you've got a good knowledge of how the GWT compiler generates Javascript code you can still reverse engineer the algorithm from the compiled code, particularly if it's generated in PRETTY mode which would pretty much be necessary if you wanted to generate an API wrapper around it.
On Monday, February 15, 2016 at 7:20:09 PM UTC-6, David wrote:
-- On Monday, February 15, 2016 at 7:20:09 PM UTC-6, David wrote:
I like to prevent my regular developers from viewing my GWT key Java source code because it contains a lot of my core business. What I like to do is following: (1). compile them into javascript. (2). use JSNI or GWT JsInterop to wrap the compiled javascript back into Java classes so my regular developers can use them in Eclipse. (3). When projects are ready for production, wrapped Java classes are replaced by a real Java classes during production compilation. Is this solution possible? Are there some examples in this community?
Thanks!
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment