[gwt-contrib] Possible compiler bug in 2.7 ignoring a set-property
Hey guys, I've found what I think is a bug in GWT2.7. We're trying to compile the attached file 'MyMegaModule.gwt.xml' The last inherit in this file is BaseBrowsers.gwt.xml - I've attached that too. In the BaseBrowsers.gwt.xml you can see that we only want gecko and safari compilations but when compiling we get an ie10 permutation too. There might be other inherits that are setting the user.agent property to something including the ie10 but because of our BaseBrowsers.gwt.xml being inherited as the last module we should only get gecko and safari, am I right? I've no idea how to fix this. Thx for any ideas! Cheers, Jan -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/ac5c7e23-fd85-46d6-883b-8f8600c496cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. MyMegaModule.gwt.xml Description: XML document BaseBrowsers.gwt.xml Description: XML document
[gwt-contrib] Re: 2.7.0 RC1 SDM not working when using java.util.List - Example attached
Ok thanks so far. Because the List.size() call is executed from GXT I don't have the possibility to change that call. I've rewritten my JsArrayListWrapper and it's not a JSO any more. So I'm good to go. Cheers, Jan Am Montag, 17. November 2014 20:22:29 UTC+1 schrieb John Stalcup: A fix for this is now committed. Which means this code snippet will now be rejected all the time. To accomplish the same thing you need to execute the .size() function dispatch (or really any function dispatch on a List instance since you've used the List interface on a JSO type) inside of a *Java* not inside of a JSNI function. This is relatively straight forward if you make a static Java function that takes a List instance and calls size() on it, and you can call this static Java function inside of your JSNI. On Wed Nov 12 2014 at 4:05:26 PM John Stalcup sta...@google.com javascript: wrote: It's more like, 50% of the time. Here's what's going on: It's currently illegal to call foo.blah() in JSNI if the variable foo is either a JSO type or interface that is implemented by some JSO type. The error you're seeing is JsniReferenceResolver enforcing this requirement, the weird part is that it should enforce it all the time but it's only enforcing it 50% of the time. The reason this is occurring is that depending on the order that JDT processes types we may or may not yet have collected the knowledge to know that the java.util.List interface is used on a JSO before JsniReferenceResolver performns its check. We need to move the correctness check to some later stage, late enough that is JSO checks will always be accurate. In the 50% of compiles that are succeeding for you right now you're actually vulnerable to runtime errors because it's outputting code that attempts to call the size() function on the prototype of the list parameter (and that will fail if the instance that is passed in happens to be a JsArrayListWrapper). On Wed Nov 12 2014 at 1:27:42 PM John Stalcup sta...@google.com javascript: wrote: I'm able to repro this both with -noincremental and -incremental, but only randomly (seems about 30% of the time). Still looking into it. On Wed Nov 12 2014 at 8:24:43 AM Thomas Broyer t.br...@gmail.com javascript: wrote: [+cc stalcup@] This might be because of incremental compilation: when JsArrayListWrapper is in another module, that module is precompiled, so the compiler knows about the type. When it's in the same module, because it's the module being compiled, it can be pruned (unused) and as consequence doesn't interfere with the JSNI checks. The workaround would be to call a static method passing the List as argument, and call the size() method in that static method, in Java-land, outside of JSNI. On Wednesday, November 12, 2014 1:39:55 PM UTC+1, Jan Thewes wrote: Hello guys, we're currently running in problems related to the SDM in GWT 2.7. We've attached two examples. JsListWrapperWorking is an example project where everything is working fine. It is CODE IDENTICAL to JsListWrapperNotWorking. In the latter one we've moved the source for the two classes JsArrayListWrapper and JsArrayWrapper to another module. No source code has been touched. When starting SDM for JsListWrapperWorking everything is working fine. When starting SDM for JsListWrapperNotWorking we get following exception: [ERROR] Errors in 'file:~/JsListWrapperNotWorking/src/ de/gad/list/client/JsListWrapperNotWorking.java' [ERROR] Line 19: Referencing interface method 'java.util.List.size()': implemented by 'de.gad.list.client.myListImpl.JsArrayListWrapper'; references to instance methods in overlay types are illegal; use a stronger type or a Java trampoline method If you need any further information I'll provide them as soon as possible! Cheers, Jan -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/21699301-33e5-4bed-a793-3ca461d681a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Logging not working anymore in GWT 2.7.0 RC
Hey guys, we've a problem with logging since testing GWT 2.7. We're using java.util.Logger() and with 2.7 any message trying to be logged with WARN or lower doesn't end up in the browser console. What I found out is that my Logger.info(String message) call is thrown away by the GWT compiler? Why does this happen? What do I have to do to get the old behavior? Cheers, Jan -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/52ec051f-318a-4f56-bc33-13dc4321a257%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Migrating to SDM-GWT 2.7.0 : SourceMaps don't load :-(
We're seeing another problem related to SourceMaps. In our case the browser executes a GET request to http://localhost:9997 /sourcemaps/systemTestModule/__HASH___sourcemap.json I don't know why the __HASH__ is not replaced...any ideas? Am Dienstag, 4. November 2014 12:18:56 UTC+1 schrieb Francois ANDRE: Hi all, I'm migrating from 2.5.1/Classical Dev Mode to 2.7.0-RC1/Super Dev Mode. I'm really exited about new features. But (yes, there is a but...) although I easily launch in SDM the basic project generated by Eclipse, It doesn't work with my real project: I launch it from Eclipse : everything seems to be good (the code server is correctly launched, then the main app). I paste the url in chrome: the first compilation automatically starts and seems to end successfully (on the Eclipse console the logs are ok) But the nothing more happens: the module don't really start. I've tried to check everywhere without founding out what's wrong. From Chrome developer tools, the only difference I've found from the execution of the simple project is that : - The http://127.0.0.1:9876/sourcemaps/myproject/x_sourcemap.json isn't called -As a consequence - I guess - on the source tab, I don't see the sourcemaps/myproject folder. However I thought I've activated sourcemaps in the module file : ... add-linker name=xsiframe / set-configuration-property name=devModeRedirectEnabled value=true / set-configuration-property name='xsiframe.failIfScriptTag' value='false' / set-property name=compiler.useSourceMaps value=true / ... If someone has faced this problem and has got the answer, I'd be really grateful. Thanks in advance François -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7.0 beta1
Hello guys, we're in the process of trying out GWT 2.7 in our massive application. Currently we get an error during compile for one module. It worked with GWT 2.6.1. Any ideas on this one? I'm not sure but the problem might be that we can't create a JSO using new ..Jso(). But the big question is why did this work in GWT 2.6.1? [ERROR] Errors in 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java' [ERROR] Line 38: Rebind result 'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot be a JSO Cheers, Jan Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
Ok thx. This is what I assumed. Will fix this and see how far we can go with 2.7. Am Dienstag, 21. Oktober 2014 12:51:45 UTC+2 schrieb Daniel Kurka: You can not create a JSO using new in Java. If this has worked with GWT 2.6.1 it is just a bug and should not have worked in the first place. -Daniel On Tue, Oct 21, 2014 at 12:46 PM, Jan Thewes jant...@gmail.com javascript: wrote: Hello guys, we're in the process of trying out GWT 2.7 in our massive application. Currently we get an error during compile for one module. It worked with GWT 2.6.1. Any ideas on this one? I'm not sure but the problem might be that we can't create a JSO using new ..Jso(). But the big question is why did this work in GWT 2.6.1? [ERROR] Errors in 'de/gad/wap/pgu/messenger/ccs/genovoice/event/impl/JsoEventFactory.java' [ERROR] Line 38: Rebind result 'de.gad.wap.pgu.messenger.ccs.genovoice.event.call.DialEvent_JsoEvt' cannot be a JSO Cheers, Jan Am Samstag, 18. Oktober 2014 19:54:40 UTC+2 schrieb Daniel Kurka: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/971ba071-e3e7-4cfb-978b-ef1fa14853a7%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Google Germany GmbH *Dienerstr. 12* *80331 München* Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a45134df-be98-4ab8-9289-7a52c8248ad7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: SeedTable is taking 6% of my applications memory
Ok I'm not sure if my seedTable guess was correct. When looking at my window object I see the seedTable property. But what you can see in my original attached screenshot is not my seedTable. Can anyone help me and tell me what it is? It's a real large bunch of Strings which take 3MB of memory. That needs to be changed. Am Freitag, 22. August 2014 14:20:56 UTC+2 schrieb Jan Thewes: Hey guys, we have a really large web application which has been developed using GWT. When launching our application and creating a Heap Snapshot using Chrome's Developer Tools we can see a large amount of memory is consumed by some properties living right under the window object. After looking into it we found out that the seedTable is taking up 6% of the whole page's heap. Because of some serious memory problems in production we are not sure what these seedTable is really used for. Can someone please explain what the seedTable is for and if there's any possibility to disable it. Any help is appreciated. Cheers, Jan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: How to trigger a click in a Frame
We've used XDM to exchange messages between the two application. Am Sonntag, 24. August 2014 17:37:52 UTC+2 schrieb Fernando Castro: I have a third party application that i want to embedded in my GWT app, however, this application is a swf, with a menu for some intro animation. I want to trigger a click the menu when the swf load to open the part that i need. Does someone have a idea? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed
Ok so I'm the only one how thinks this might be a problem for us. We're using GWT in a real large company environment (core banking system) and to create a baseline we have to use our companies build server. These are currently running on Java6. I've already reached out to get an information when the Java compile level will be increased. This is just my opinion speaking for a real large company. Am Donnerstag, 11. September 2014 19:50:53 UTC+2 schrieb Daniel Kurka: Hi all, while bringing GSS support into GWT, I discovered that the closure styleheets compiler actually requires Java7. This means that we either have to do a back port of the compiler (I haven't looked at it seriously) or require Java7 for development with GWT (probably only if you are using CssResource). I really like your input on this and if I do not hear any strong objections, I will go ahead with using the Java7 version of closure stylesheets and thus we will require Java7 for GWT development. Note: This does not impact deployment of any GWT apps. You can still run a GWT app on a Java6 container, this will only affect developers on their machines. -Daniel -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a054c77d-725e-4559-9a35-441c2b416387%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Compile Error after switching to 2.6 in first compile run
I understand your points BUT one thing. If I compile my modules alone I don't get any compile error. So compiling every single module works. It has to do something with the order and caches. I just can't nail it down. We're running a real real big GWT application here. I'm close to go back to 2.5.1 because the compiles fail too often but not always... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Compile Error after switching to 2.6 in first compile run
Well, the order has to do something with the failing compile. But this is new with GWT 2.6. Before our compilation always worked. And we don't have changed our code since the change to 2.6. Still need ideas what this can be. In my opinion this is a GWT internal bug. Am Dienstag, 11. Februar 2014 18:20:38 UTC+1 schrieb BGL: I would say that the order of compilation is not the one you expect. The error Line 23: No source code is available for type de.gad.gfw.web.navigator.menu.model.MenuElement; did you forget to inherit a required module? Errors in 'file:/Users/xgadjth/sandboxes/b21_gwt-03.03.00/render/source/de/gad/gfw/web/gui/render/dialog/print/PrintMenu.java' Line 8: The hierarchy of the type PrintMenu is inconsistent says that you do not have the class file in your compilation classpath. Then, for any reason, the jar or the class file (with its source) is found in the classpath and the compilation is working.Difficult to say without the build process. Compare the order when you compile module per module and full automated. There must be a difference. Or do you deploy resources when you compile one by one ? This would publish some jar somewhere that are theun used by the first project... 2014-02-11 17:09 GMT+01:00 Jan Thewes jant...@gmail.com javascript:: Ok any further information. We're trying to compile 5 modules at a time. That fails When compiling all the 5 modules alone. It works! We also have a merge-module. These combines 4 of our 5 modules. This merge module compiles without any error, too! So this is a real strange behavior... Am Dienstag, 11. Februar 2014 09:25:05 UTC+1 schrieb Jan Thewes: Hey guys, we have a very strange problem here. We've a real large application written in GWT using GXT. We wanted to switch to 2.6 because we need IE10 support. For that reason we patched the GXT 2.3.1 source so that it works with GWT 2.6. We now have the problem that the first compile fails. After the compile failed I start the compile again and it ends successful. I don't really know what the problem is. I added the compile log. There you can see that the compile fails with an error related to AutoHidePreventMenu (line 966) I added a detail log where you can see the error in more detail (compiled with output Debug). Any help is appreciated. If I can provide any further information feel free to ask! Cheers, Jan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com javascript:. To post to this group, send email to google-we...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Re: Compile Error after switching to 2.6 in first compile run
Ok any further information. We're trying to compile 5 modules at a time. That fails When compiling all the 5 modules alone. It works! We also have a merge-module. These combines 4 of our 5 modules. This merge module compiles without any error, too! So this is a real strange behavior... Am Dienstag, 11. Februar 2014 09:25:05 UTC+1 schrieb Jan Thewes: Hey guys, we have a very strange problem here. We've a real large application written in GWT using GXT. We wanted to switch to 2.6 because we need IE10 support. For that reason we patched the GXT 2.3.1 source so that it works with GWT 2.6. We now have the problem that the first compile fails. After the compile failed I start the compile again and it ends successful. I don't really know what the problem is. I added the compile log. There you can see that the compile fails with an error related to AutoHidePreventMenu (line 966) I added a detail log where you can see the error in more detail (compiled with output Debug). Any help is appreciated. If I can provide any further information feel free to ask! Cheers, Jan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
Problem deploying GWT on IIS and Tomcat
I've set up an environment where IIS runs on one server and the RPC
endpoints and servlets run on another machine on Tomcat.
The site is available entering http://appName
I've enabled URL Rewriting in IIS so that every call to
http://appName/appService
is redirected to http://tomcatMachine/appName/{R:0}
The service call are reaching the application on tomcat but the there
i get an error which says that my Class won't be serialized because
MD5.gwt.rpc can't be found.
What am I doing wrong?
Best Regards
Jan
--
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.
