Using Object in classes passed via GWT RPC
Hi It passed a little bit of time from when I was programming in GWT, but backthen you could pass only objects that implemented Serializable interface ... Or, even before that, an interface named IsSerializable by GWT. So in your case, instead of type Object I would try to use Serializable. Hope it helps. Have a nice day -- 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.
Celltable column filter
Hi guys, I am wondering if there is any way to filter coulmn of a CellTable. UI should should be something like this - column should have a drop down icon, clicking on this icon a text filed should appear for searching through the column. I know this can be done using datagrid but is it possible to do with CellTable? Thanks! -- 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.
[SOLVED] Re: OutOfMemoryError after upgrade to OS X Mavericks
Hi, Upgrading to the latest version of the jdk fixed the issue. It should be interesting if I had reinstalled the same version, I think it would have worked too. Thanks to Cristiano for the tip and to everyone for the help. Eddy -- 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: Firefox in OS X freezes in DevMode.
Thanks Colin, yeah that's what I figured, initially I thought that it would be a problem in the plugin given that it was only blocking Firefox and only in OS X (given that Chrome worked and also Firefox but under Linux). I started debugging and got all the way there. I doubt that it's a breakpoint or having to wait for a long time as I did leave the browser for a few minutes, there's no breakpoints and CPU is not peaking, so I'd think there's something else waiting. I'll follow your suggestion and check now the other side, but it's good to know that you haven't had an issue with FF and Mavericks as then that would sadly imply that there's something wrong with my computer :(. On Friday, November 8, 2013 9:20:10 PM UTC-5, Colin Alworth wrote: Line 155: ssize_t n = recv(sock, readBuf, BUF_SIZE, 0); That seems to say 'block until bytes are written by the other end of the socket', or in other words, wait until the JVM is ready to go. Are you sure that the IDE isn't paused on a breakpoint, or that you have waited long enough for the page to load? When the browser is in this state, try pausing the JVM to see what the dev mode thread is doing - I'm betting it is hard at work on something... but if it too is waiting for something, that could be a problem. But the recv call is *supposed* to block, at least until dev mode has finished running its not-yet-JS code. We've had no issues with Mavericks and latest FF in our projects fwiw, aside from the usual 'dev mode takes longer to do anything' fun. On Thursday, November 7, 2013 10:59:18 PM UTC-6, Carlos Aguayo wrote: It's getting stuck in line 155 in: https://gwt.googlesource.com/gwt-plugins/+/master/common/Socket.cpp On Thursday, November 7, 2013 7:32:28 PM UTC-5, Carlos Aguayo wrote: I'm started to have issues when trying to use DevMode with Firefox in OS X and the only thing new is that I upgraded to Mavericks. Here's what I see: I create a GWT sample app (the default one that comes with the Eclipse GWT plugin), I launch dev mode and try to access it with Firefox, as soon as I paste the address, the browser freezes. It stays frozen until I stop development mode, once I do that, Firefox comes back to life. Using Chrome is fine. I also have a VM setup with Linux and Firefox, if I try to debug through that Firefox, everything works as well. I tried to see if there was any sort of deadlock in the devmode plugin by using jconsole but it says that there's no deadlock. I have already ensured that Firefox is clean by doing a Reset Firefox Apparently the only thing that fixes this issue is by creating a new profile. After I create a new profile, I only install the GWT plugin and works for a few days, then it freezes again. I don't install anything else in Firefox. I have tried different versions of Firefox (21, 24 and 25) and I see the same behavior in all of them. I was wondering if anyone else could be seeing something similar and/or would have any suggestions as to how to debug the GWT extension to try to figure out what's going on? -- 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.
Using Object in classes passed via GWT RPC
Why do you have super() in you constructor? Your class does not extend anything. -- 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: Using Object in classes passed via GWT RPC
Cargo cult programming, born of desperation. I have another class that is working correctly with a field of type Object, so I was analyzing it and trying to eliminate each difference as a possible cause. The other class happens to pitch to the zero-argument Object constructor, so I added it to this class as well. It didn't help, of course. On Saturday, November 9, 2013 10:49:20 AM UTC-7, Patrick Tucker wrote: Why do you have super() in you constructor? Your class does not extend anything. -- 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: Using Object in classes passed via GWT RPC
change field - ListLocalizedMessage errors to ArrayListLocalizedMessage errors and see whether it works On Sat, Nov 9, 2013 at 11:46 PM, James Clough cloug...@gmail.com wrote: Cargo cult programming, born of desperation. I have another class that is working correctly with a field of type Object, so I was analyzing it and trying to eliminate each difference as a possible cause. The other class happens to pitch to the zero-argument Object constructor, so I added it to this class as well. It didn't help, of course. On Saturday, November 9, 2013 10:49:20 AM UTC-7, Patrick Tucker wrote: Why do you have super() in you constructor? Your class does not extend anything. -- 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. -- Nagin Kothari Co-founder, Zilicus Solutions www.zilicus.com -- 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: Firefox in OS X freezes in DevMode.
If you can repro this on at least one other machine and get the details of what the JVM is doing, that'd be helpful. I have a very basic familiarity with the dev mode code from researching the FF dev mode memory leak, and would be happy to take a closer look. From your description it sounds like the JVM is either also waiting for the browser (and we'll need to figure out how it got into that bad state with one having ignored a message from the other), or the JVM is blocked on something else entirely, the real source of the bug. My bet is on the latter, that something funny is going on there. Recent updates to Dev Mode were made for all platforms, nothing mac-specific, so that seems unlikely. Getting an old copy of firefox and an old (pre-ff25) copy of the plugin would probably be worth testing as well if you are able to repro this on more than one box. Note: the FF-devmode memory leak has to do with the old pages failing to shut down the plugin correctly, so make certain that you don't load more than once. If you do, your JVM will have two different threads trying to talk to the browser, and it may be difficult to tell which one is the current one, versus the 'memory leak' one. On Saturday, November 9, 2013 11:01:40 AM UTC-6, Carlos Aguayo wrote: Thanks Colin, yeah that's what I figured, initially I thought that it would be a problem in the plugin given that it was only blocking Firefox and only in OS X (given that Chrome worked and also Firefox but under Linux). I started debugging and got all the way there. I doubt that it's a breakpoint or having to wait for a long time as I did leave the browser for a few minutes, there's no breakpoints and CPU is not peaking, so I'd think there's something else waiting. I'll follow your suggestion and check now the other side, but it's good to know that you haven't had an issue with FF and Mavericks as then that would sadly imply that there's something wrong with my computer :(. On Friday, November 8, 2013 9:20:10 PM UTC-5, Colin Alworth wrote: Line 155: ssize_t n = recv(sock, readBuf, BUF_SIZE, 0); That seems to say 'block until bytes are written by the other end of the socket', or in other words, wait until the JVM is ready to go. Are you sure that the IDE isn't paused on a breakpoint, or that you have waited long enough for the page to load? When the browser is in this state, try pausing the JVM to see what the dev mode thread is doing - I'm betting it is hard at work on something... but if it too is waiting for something, that could be a problem. But the recv call is *supposed* to block, at least until dev mode has finished running its not-yet-JS code. We've had no issues with Mavericks and latest FF in our projects fwiw, aside from the usual 'dev mode takes longer to do anything' fun. On Thursday, November 7, 2013 10:59:18 PM UTC-6, Carlos Aguayo wrote: It's getting stuck in line 155 in: https://gwt.googlesource.com/gwt-plugins/+/master/common/Socket.cpp On Thursday, November 7, 2013 7:32:28 PM UTC-5, Carlos Aguayo wrote: I'm started to have issues when trying to use DevMode with Firefox in OS X and the only thing new is that I upgraded to Mavericks. Here's what I see: I create a GWT sample app (the default one that comes with the Eclipse GWT plugin), I launch dev mode and try to access it with Firefox, as soon as I paste the address, the browser freezes. It stays frozen until I stop development mode, once I do that, Firefox comes back to life. Using Chrome is fine. I also have a VM setup with Linux and Firefox, if I try to debug through that Firefox, everything works as well. I tried to see if there was any sort of deadlock in the devmode plugin by using jconsole but it says that there's no deadlock. I have already ensured that Firefox is clean by doing a Reset Firefox Apparently the only thing that fixes this issue is by creating a new profile. After I create a new profile, I only install the GWT plugin and works for a few days, then it freezes again. I don't install anything else in Firefox. I have tried different versions of Firefox (21, 24 and 25) and I see the same behavior in all of them. I was wondering if anyone else could be seeing something similar and/or would have any suggestions as to how to debug the GWT extension to try to figure out what's going on? -- 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: Testing w/Selenium against app running in Eclipse demands Firefox Development Mode Plugin
By default, Selenium starts the browser with a fresh profile every time, which means that it has no plugins installed. On quitting, it deletes that profile again, to make sure that it won't slowly consume your disk. When you start the firefox driver instance, you can ask it to load profile details, including plugins. You can either create a new profile that only has this plugin added (to keep things simpler and avoid other plugin issues), or you can actually use your own default profile. http://steveliles.github.io/testing_gwt_apps_in_dev_mode_with_webdriver.html documents using your own profile, but this requires already having a firefox profile set up locally with dev mode, which may not be ideal for using other test machines to verify your app. https://groups.google.com/d/topic/webdriver/xPDudSnAxwo/discussion documents doing this the other way around, using the default of a fresh profile (no history, no cache, no plugins, etc), and adding the gwt dev mode plugin. On Wednesday, November 6, 2013 2:37:17 PM UTC-6, Jeff Levene wrote: Using GWT 2.4.0, Eclipse Kepler, Firefox 25.0, JDK 1.7.0_40, TestNG 6.8.5 When I run my test suite against the GWT app running on a Tomcat server, all is well. When I try to run it against a local copy running in Eclipse, instead of bringing up my application, Firefox gives me: Development Mode requires the GWT Developer Plugin with a badge to click on to download the plugin. It does this no matter how many times I have downloaded and installed the plugin and re-started Firefox. Ideas? -- 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.
GWT-DnD on Viewport and Google Maps like Map
I use GWT-dnd https://code.google.com/p/gwt-dnd/ to make a viewport
draggable. A viewport is fixed size window that shows a part of a larger
map. As illustrated in the following image:
[image: enter image description here]
I followed this post: Move ViewPort of Element Map in
GWT?http://stackoverflow.com/questions/19433813/move-viewport-of-element-map-in-gwt
which
works fine, but I could not get it get to work with GWT-dnd. GWT-dnd.
I created the following simple scenario:
[image: enter image description here]
My problem is that I could GWT-dnd make working only if the drag panel is
smaller than the drop panel. In my case the map (canvas), which is the
yellow box, is much bigger than the viewport. If I make the viewport as the
drop area and the map draggable then it does not work. When I try to drag
the map it will be adjusted by one boundary of the viewport and that's it.
What is want is the following: When is drag the map (the part of the map
that is visible in the viewport) than the position of the map should
change. For example when I drag the map down I get what I show in the
following image:
[image: enter image description here]
What the user actually sees is the following:
[image: enter image description here]
Here is what I did in my ScreenView.ui.xml file:
g:AbsolutePanel ui:field=viewport
addStyleNames={resources.screenCss.viewportContainer}
g:FocusPanel ui:field=canvasFocus
addStyleNames={resources.screenCss.focusPanel}
g:AbsolutePanel ui:field=canvas
addStyleNames={resources.screenCss.canvas}
g:HTMLPanel
addStyleNames={resources.screenCss.mapContainer}
g:FlowPanel ui:field=test1
addStyleNames={resources.screenCss.test1}
g:HTMLtest1/g:HTML
/g:FlowPanel
g:FlowPanel ui:field=test2
addStyleNames={resources.screenCss.test2}
g:HTMLtest2/g:HTML
/g:FlowPanel
/g:HTMLPanel
/g:AbsolutePanel
/g:FocusPanel
/g:AbsolutePanel
In my ScreeView.java I do:
@UiFieldAbsolutePanel viewport;
@UiFieldAbsolutePanel canvas;
@UiFieldFlowPanel test1;
private PickupDragController dragController;private DropController
dropController;
// create drag controller
dragController = new PickupDragController(viewport, true);
// create drop controller
dropController = new AbsolutePositionDropController(canvas);
dragController.registerDropController(dropController);
// make test1 draggable
FocusPanel focusPanel = new FocusPanel();
focusPanel.addStyleName(resources.screenCss().noteFocusPanel());
test1.add(focusPanel);
canvas.add(test1);
dragController.makeDraggable(test1, focusPanel);
Now I have a red rectangle draggable.
*How can I make my map (canvas) draggable?*
*Here is the link to my Stackoverflow question:
**http://stackoverflow.com/questions/19761185/gwt-drag-and-drop-for-draggable-viewport
http://stackoverflow.com/questions/19761185/gwt-drag-and-drop-for-draggable-viewport*
--
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: Firefox in OS X freezes in DevMode.
I really appreciate your help Colin. At this point I believe it's some misconfiguration in my computer. I tried to do a jconsole on the devmode process and it said it couldn't connect to it. I then did a jstack and said the same but this time the utility suggested to use a -F to force it, when I did that, I was able to see the threads. I then tried to launch firefox and sudo mode, and voila, that worked! So I open Firefox in normal mode, it can't connect to the plugin, I then try it in root mode and works... The devmode process and eclipse are running with my account, so I can't tell what else I could have messed up but the important is that I can work and move on. I appreciate the help, On Saturday, November 9, 2013 3:10:58 PM UTC-5, Colin Alworth wrote: If you can repro this on at least one other machine and get the details of what the JVM is doing, that'd be helpful. I have a very basic familiarity with the dev mode code from researching the FF dev mode memory leak, and would be happy to take a closer look. From your description it sounds like the JVM is either also waiting for the browser (and we'll need to figure out how it got into that bad state with one having ignored a message from the other), or the JVM is blocked on something else entirely, the real source of the bug. My bet is on the latter, that something funny is going on there. Recent updates to Dev Mode were made for all platforms, nothing mac-specific, so that seems unlikely. Getting an old copy of firefox and an old (pre-ff25) copy of the plugin would probably be worth testing as well if you are able to repro this on more than one box. Note: the FF-devmode memory leak has to do with the old pages failing to shut down the plugin correctly, so make certain that you don't load more than once. If you do, your JVM will have two different threads trying to talk to the browser, and it may be difficult to tell which one is the current one, versus the 'memory leak' one. On Saturday, November 9, 2013 11:01:40 AM UTC-6, Carlos Aguayo wrote: Thanks Colin, yeah that's what I figured, initially I thought that it would be a problem in the plugin given that it was only blocking Firefox and only in OS X (given that Chrome worked and also Firefox but under Linux). I started debugging and got all the way there. I doubt that it's a breakpoint or having to wait for a long time as I did leave the browser for a few minutes, there's no breakpoints and CPU is not peaking, so I'd think there's something else waiting. I'll follow your suggestion and check now the other side, but it's good to know that you haven't had an issue with FF and Mavericks as then that would sadly imply that there's something wrong with my computer :(. On Friday, November 8, 2013 9:20:10 PM UTC-5, Colin Alworth wrote: Line 155: ssize_t n = recv(sock, readBuf, BUF_SIZE, 0); That seems to say 'block until bytes are written by the other end of the socket', or in other words, wait until the JVM is ready to go. Are you sure that the IDE isn't paused on a breakpoint, or that you have waited long enough for the page to load? When the browser is in this state, try pausing the JVM to see what the dev mode thread is doing - I'm betting it is hard at work on something... but if it too is waiting for something, that could be a problem. But the recv call is *supposed* to block, at least until dev mode has finished running its not-yet-JS code. We've had no issues with Mavericks and latest FF in our projects fwiw, aside from the usual 'dev mode takes longer to do anything' fun. On Thursday, November 7, 2013 10:59:18 PM UTC-6, Carlos Aguayo wrote: It's getting stuck in line 155 in: https://gwt.googlesource.com/gwt-plugins/+/master/common/Socket.cpp On Thursday, November 7, 2013 7:32:28 PM UTC-5, Carlos Aguayo wrote: I'm started to have issues when trying to use DevMode with Firefox in OS X and the only thing new is that I upgraded to Mavericks. Here's what I see: I create a GWT sample app (the default one that comes with the Eclipse GWT plugin), I launch dev mode and try to access it with Firefox, as soon as I paste the address, the browser freezes. It stays frozen until I stop development mode, once I do that, Firefox comes back to life. Using Chrome is fine. I also have a VM setup with Linux and Firefox, if I try to debug through that Firefox, everything works as well. I tried to see if there was any sort of deadlock in the devmode plugin by using jconsole but it says that there's no deadlock. I have already ensured that Firefox is clean by doing a Reset Firefox Apparently the only thing that fixes this issue is by creating a new profile. After I create a new profile, I only install the GWT plugin and works for a few days, then it freezes again. I don't install anything else in Firefox. I have tried different versions of Firefox (21, 24 and 25) and I
Re: [gwt-contrib] Re: Reminder: Branching GWT 2.6 later today
I mean the permutation for IE11 On Friday, November 8, 2013 4:34:09 PM UTC+8, Matthew Dempsky wrote: On Thu, Nov 7, 2013 at 9:28 PM, Li Bin orno...@gmail.com javascript:wrote: Is it possible for 2.6 to support IE11 in the final release ? It's unclear to me what you mean by supporting IE11. If you know of issues between GWT and IE11, please report them at https://code.google.com/p/google-web-toolkit/issues/list. However, it's unlikely that any new IE11-specific changes will be submitted between now and 2.6.0's release. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] GWT 2.6 and Java 6
You are right, there should be an extra option -sourceLevel auto and that should be the default for devmode. On Nov 8, 2013, at 17:47, Colin Alworth niloc...@gmail.com wrote: Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we want our code to work with anyone who chooses to use Java 6 as well - and I surmised that GWT had the same goal. Would it make sense to consider a warning indicating that the flag is needed with Java 6, or auto-detecting that Java 6 is running so a JavaScriptObject$ compiled for 7 can't possibly work? On Friday, November 8, 2013 6:01:40 PM UTC-6, Roberto Lublinerman wrote: You should be able to invoke devmode with -sourceLevel 6. Roberto Lublinerman | Software Engineer | rlu...@google.com javascript: | 408-500-9148 On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth nilo...@gmail.comjavascript: wrote: I'm not yet convinced that this isn't either a) a workspace issue or b) a decision the community reached and I missed, but I figured I should stick it out there and see if someone can correct me. I've just brought our project up to date with GWT 2.6.0-rc1 from maven, and I can verify that the class files have magic number 50.0 set on them, indicating Java 6. I can compile the project with a Java 6 jdk, and gwtc behaves as expected, but I can't run dev mode. The error I get usually goes a little like this: ERROR: Unable to initialize static dispatcher java.lang.UnsupportedClassVersionError: com/google/gwt/core/client/JavaScriptObject$ : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121) at com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:249) at com.google.gwt.dev.shell.JsValueGlue.set(JsValueGlue.java:220) The magic number 51.0 indicates Java7 - how is it that while I'm running Java 6, I am generating Java 7-only classes? My working theory is that since we moved some internals to be Java 7 capable (somewhere around https://gwt.googlesource.com/gwt/+/e4f6142 or a related commit), it was set as the default. My question: do we intend to require Java 7 for dev mode (and therefore also GWTTestCase run in dev mode), but allow Java 6 for essentially everything else? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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.comjavascript: . For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] GWT 2.6 and Java 6
Thanks for the clarification, I'll take a quick stab to see if I can make that change on my own. On Nov 9, 2013 5:40 PM, Roberto Lublinerman rlu...@google.com wrote: You are right, there should be an extra option -sourceLevel auto and that should be the default for devmode. On Nov 8, 2013, at 17:47, Colin Alworth niloc...@gmail.com wrote: Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we want our code to work with anyone who chooses to use Java 6 as well - and I surmised that GWT had the same goal. Would it make sense to consider a warning indicating that the flag is needed with Java 6, or auto-detecting that Java 6 is running so a JavaScriptObject$ compiled for 7 can't possibly work? On Friday, November 8, 2013 6:01:40 PM UTC-6, Roberto Lublinerman wrote: You should be able to invoke devmode with -sourceLevel 6. Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148 On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth nilo...@gmail.com wrote: I'm not yet convinced that this isn't either a) a workspace issue or b) a decision the community reached and I missed, but I figured I should stick it out there and see if someone can correct me. I've just brought our project up to date with GWT 2.6.0-rc1 from maven, and I can verify that the class files have magic number 50.0 set on them, indicating Java 6. I can compile the project with a Java 6 jdk, and gwtc behaves as expected, but I can't run dev mode. The error I get usually goes a little like this: ERROR: Unable to initialize static dispatcher java.lang.UnsupportedClassVersionError: com/google/gwt/core/client/JavaScriptObject$ : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.lang.ClassLoader.defineClass(ClassLoader.java:471) at com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121) at com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:249) at com.google.gwt.dev.shell.JsValueGlue.set(JsValueGlue.java:220) The magic number 51.0 indicates Java7 - how is it that while I'm running Java 6, I am generating Java 7-only classes? My working theory is that since we moved some internals to be Java 7 capable (somewhere around https://gwt.googlesource.com/gwt/+/e4f6142 or a related commit), it was set as the default. My question: do we intend to require Java 7 for dev mode (and therefore also GWTTestCase run in dev mode), but allow Java 6 for essentially everything else? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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 . For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
