Re: Designer Problems after GWT 2.3 install
Thanks for the work around. It works for me! I installed a new fresh eclipse and gwt plugin into a directory without spaces. On 6 Maj, 00:46, Eric Clayberg clayb...@google.com wrote: See the latest update to... http://code.google.com/p/google-web-toolkit/issues/detail?id=6316 We hope to have a patch out tomorrow. In the meantime, a work around is available. On May 5, 2:09 pm, Ian Jacobs ian.jac...@gmail.com wrote: I take it back. My 1st test was using a gwt plugin I installed into a directory with spaces. I changed the classpath to use the gwt plugin off of c:\eclipse\ and the designer loaded without incident. -- 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.
Re: Designer Problems after GWT 2.3 install
OK I HAVE FOUND THE SOLUTION, make sure there are no spaces in your workspace path if this is the first time you installing GWT. If you updating then make sure you uninstall the current version of you designer which in most cases would be 2.2 and install a fresh 2.3 copy. Sent from my iPhone On May 6, 2011, at 0:46, Eric Clayberg clayb...@google.com wrote: See the latest update to... http://code.google.com/p/google-web-toolkit/issues/detail?id=6316 We hope to have a patch out tomorrow. In the meantime, a work around is available. On May 5, 2:09 pm, Ian Jacobs ian.jac...@gmail.com wrote: I take it back. My 1st test was using a gwt plugin I installed into a directory with spaces. I changed the classpath to use the gwt plugin off of c:\eclipse\ and the designer loaded without incident. -- 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. -- 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.
Re: Designer Problems after GWT 2.3 install
I don't see this being solved anytime soon. We need a work around. Sent from my iPhone On May 5, 2011, at 0:09, Tim troes...@gmail.com wrote: A co-worker and I are having the exact same issue as the original poster in both Eclipse 3.5 and 3.6. I even setup a fresh installation of Eclipse 3.6, downloaded all the plugins, and created an example GWT project and it still didn't work. We have been fighting this all day as well and made no progress. Tim On May 4, 5:07 pm, CTO_Mike michael.daco...@gmail.com wrote: I have the same story with the exact same error message (NullPointerException, java.io.File, etc.). I have been banging my head against this one all day with no luck! GWT team please help! - Mike On May 4, 4:45 pm, Joe D. jad...@gmail.com wrote: Hi, I upgraded this AM to 2.3, and have not been able to launch the designer since. I went as far a reinstalling helios-SR2 and reinstalling the latest versions of the plugin and designer. I get this message even with a brand new out of the box web app. I've searched around and can't find any references. Woe is me... Any help would be really appreciated! Thanks, Joe Internal Error GWT Designer encountered unexpected internal error. This could be caused by a GWT Designer bug or by a misconfiguration issue, conflict, partial update, etc. Show stack trace. Hide stack trace. Stack trace: java.lang.NullPointerException at java.io.File.init(Unknown Source) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.getSharedClassLoader(HostedModeSupport.java:225) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.createClassLoaders(HostedModeSupport.java:117) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.init(HostedM odeSupport.java:66) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupportFactory.create(HostedModeSupportFactory.java:19) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.getHostedModeSupport(GwtState.java:1188) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize0( GwtState.java:234) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(G wtState.java:210) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFac tory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoader(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFac tory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(Java InfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.jav a:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser. java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoPars er.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoPars er.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(E xecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.jav a:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPa ge.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455 ) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.ja va:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.j ava:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:404) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPa ge.java:354) at org.eclipse.wb.internal.core.editor.UndoManager.refreshDesignerEditor(UndoM anager.java:381) at org.eclipse.wb.internal.core.editor.UndoManager.activate(UndoManager.java:9 0) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState_True(Desig nPage.java:247) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState(DesignPage .java:225) at
Re: Designer Problems after GWT 2.3 install
Well, I've come up with a (sad excuse for) workaround. When I reverted to 2.0.4 I was at least able to get the Designer to come up. 2.2.0 was unsuccessful. But that of course generated two other issues: - Can't use the new cell features -- can live with that for now - Get the dreaded generic plugin failure when I try to run as a GWT app from Eclipse At the moment they are only sucky inconveniences as I'm not using cells that much yet and was able to back them out. And I can still deploy the app via Tomcat and it works. But this is definitely not a reason for the GWT folks to pop open a beer. Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. While I'm in a whiny mood, I tried to downgrade to the previous GPE but could not find it. So another question for the GWT folks -- where is it hiding? Or do you suggest doing a full backup of my Eclipse install before a seemingly harmless upgrade to the latest GWT? I backup my Workspace hourly, but usually save the Eclipse install for anticipated big changes. GWT is a GREAT product, please keep it the best of breed it is and treat this as a Priority 1! Thanks, Joe -- 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.
Re: Designer Problems after GWT 2.3 install
Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. I just did the same and it works for me. 0. Java(TM) SE Runtime Environment (build 1.6.0_25-b06); 1. Extract Eclipse IDE for Java Developers 3.6.2; 2. Install GPE from http://code.google.com/intl/en/eclipse/docs/download.html with GWT and AppEngine SDK; 3. Create New Web Application Project with name test and package com.example.myproject; 4. open generated Test.java with GWT Designer editor; 5. no exception. -- 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.
Re: Designer Problems after GWT 2.3 install
This exception basically tell us that gwt-dev.jar can't be found on your project classpath. Without additional context, this could be the result of many different things. Some possibilities: 1) Incomplete installation/update. 2) Multiple versions of GWT on the classpath 3) Old version of GWT Designer still installed 4) Maven problem As Konstantin mentioned, just posting a stack trace fragment like this does not tell us much. We need to see the complete error log, project classpath, Eclipse configuration, etc. The error window includes a button that will generate a complete error report (ZIP file) with all the pieces needed to analyze an exception like this. If you don't want to send that, then we at least need to see the entire Eclipse .metadata .log file (not just a stack fragment) and your complete Eclipse Help About Installation Details Configuration. In the mean time, here are some things you can try based on 1-4 above: 0) Make sure that gwt-dev.jar appears on your project classpath 1) Do a new install into a new, clean Eclipse environment 2) Check your project classpath and make sure that gwt-user appears once 3) If you have an old version of GWT Designer installed (v8.1.1 or earlier), un-install it 4) Copy gwt-dev.jar (with its original name) to the same Maven folder as gwt-user.jar On May 4, 4:45 pm, Joe D. jad...@gmail.com wrote: Hi, I upgraded this AM to 2.3, and have not been able to launch the designer since. I went as far a reinstalling helios-SR2 and reinstalling the latest versions of the plugin and designer. I get this message even with a brand new out of the box web app. I've searched around and can't find any references. Woe is me... Any help would be really appreciated! Thanks, Joe Internal Error GWT Designer encountered unexpected internal error. This could be caused by a GWT Designer bug or by a misconfiguration issue, conflict, partial update, etc. Show stack trace. Hide stack trace. Stack trace: java.lang.NullPointerException at java.io.File.init(Unknown Source) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.getSharedClass Loader(HostedModeSupport.java:225) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.createClassLoa ders(HostedModeSupport.java:117) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.init(HostedM odeSupport.java:66) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupportFactory.create( HostedModeSupportFactory.java:19) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.getHostedMod eSupport(GwtState.java:1188) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize0( GwtState.java:234) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(G wtState.java:210) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFac tory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoa der(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFac tory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(Java InfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.jav a:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser. java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoPars er.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoPars er.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(E xecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.jav a:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPa ge.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455 ) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.ja va:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.j ava:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProg ress(DesignPage.java:404) at
Re: Designer Problems after GWT 2.3 install
I have the exact same problem. I have created an issue here http://code.google.com/p/google-web-toolkit/issues/detail?id=6316. Please go there and vote for it (click at the star). Joe, please let us know if you find a better workaround :) Harald On 5 Maj, 14:13, Joe D. jad...@gmail.com wrote: Well, I've come up with a (sad excuse for) workaround. When I reverted to 2.0.4 I was at least able to get the Designer to come up. 2.2.0 was unsuccessful. But that of course generated two other issues: - Can't use the new cell features -- can live with that for now - Get the dreaded generic plugin failure when I try to run as a GWT app from Eclipse At the moment they are only sucky inconveniences as I'm not using cells that much yet and was able to back them out. And I can still deploy the app via Tomcat and it works. But this is definitely not a reason for the GWT folks to pop open a beer. Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. While I'm in a whiny mood, I tried to downgrade to the previous GPE but could not find it. So another question for the GWT folks -- where is it hiding? Or do you suggest doing a full backup of my Eclipse install before a seemingly harmless upgrade to the latest GWT? I backup my Workspace hourly, but usually save the Eclipse install for anticipated big changes. GWT is a GREAT product, please keep it the best of breed it is and treat this as a Priority 1! Thanks, Joe -- 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.
Re: Designer Problems after GWT 2.3 install
Thanks for posting the error report in the issue, Harald. We're looking into it. /dmc On Thu, May 5, 2011 at 8:31 AM, harald harald.ander...@gmail.com wrote: I have the exact same problem. I have created an issue here http://code.google.com/p/google-web-toolkit/issues/detail?id=6316. Please go there and vote for it (click at the star). Joe, please let us know if you find a better workaround :) Harald On 5 Maj, 14:13, Joe D. jad...@gmail.com wrote: Well, I've come up with a (sad excuse for) workaround. When I reverted to 2.0.4 I was at least able to get the Designer to come up. 2.2.0 was unsuccessful. But that of course generated two other issues: - Can't use the new cell features -- can live with that for now - Get the dreaded generic plugin failure when I try to run as a GWT app from Eclipse At the moment they are only sucky inconveniences as I'm not using cells that much yet and was able to back them out. And I can still deploy the app via Tomcat and it works. But this is definitely not a reason for the GWT folks to pop open a beer. Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. While I'm in a whiny mood, I tried to downgrade to the previous GPE but could not find it. So another question for the GWT folks -- where is it hiding? Or do you suggest doing a full backup of my Eclipse install before a seemingly harmless upgrade to the latest GWT? I backup my Workspace hourly, but usually save the Eclipse install for anticipated big changes. GWT is a GREAT product, please keep it the best of breed it is and treat this as a Priority 1! Thanks, Joe -- 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. -- David Chandler Developer Programs Engineer, Google Web Toolkit w: http://code.google.com/ b: http://googlewebtoolkit.blogspot.com/ t: @googledevtools -- 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.
Re: Designer Problems after GWT 2.3 install
Yes, thank you for the report. That should be very helpful. We are looking at it now. On May 5, 8:31 am, harald harald.ander...@gmail.com wrote: I have the exact same problem. I have created an issue herehttp://code.google.com/p/google-web-toolkit/issues/detail?id=6316. Please go there and vote for it (click at the star). Joe, please let us know if you find a better workaround :) Harald On 5 Maj, 14:13, Joe D. jad...@gmail.com wrote: Well, I've come up with a (sad excuse for) workaround. When I reverted to 2.0.4 I was at least able to get the Designer to come up. 2.2.0 was unsuccessful. But that of course generated two other issues: - Can't use the new cell features -- can live with that for now - Get the dreaded generic plugin failure when I try to run as a GWT app from Eclipse At the moment they are only sucky inconveniences as I'm not using cells that much yet and was able to back them out. And I can still deploy the app via Tomcat and it works. But this is definitely not a reason for the GWT folks to pop open a beer. Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. While I'm in a whiny mood, I tried to downgrade to the previous GPE but could not find it. So another question for the GWT folks -- where is it hiding? Or do you suggest doing a full backup of my Eclipse install before a seemingly harmless upgrade to the latest GWT? I backup my Workspace hourly, but usually save the Eclipse install for anticipated big changes. GWT is a GREAT product, please keep it the best of breed it is and treat this as a Priority 1! Thanks, Joe -- 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.
Re: Designer Problems after GWT 2.3 install
We are suspecting some weird issue when Eclipse is installed to a path with spaces in it. Can you try it using an Eclipse installed into a path w/o spaces and let us know if it makes any difference? On May 5, 10:35 am, Eric Clayberg clayb...@google.com wrote: Yes, thank you for the report. That should be very helpful. We are looking at it now. On May 5, 8:31 am, harald harald.ander...@gmail.com wrote: I have the exact same problem. I have created an issue herehttp://code.google.com/p/google-web-toolkit/issues/detail?id=6316. Please go there and vote for it (click at the star). Joe, please let us know if you find a better workaround :) Harald On 5 Maj, 14:13, Joe D. jad...@gmail.com wrote: Well, I've come up with a (sad excuse for) workaround. When I reverted to 2.0.4 I was at least able to get the Designer to come up. 2.2.0 was unsuccessful. But that of course generated two other issues: - Can't use the new cell features -- can live with that for now - Get the dreaded generic plugin failure when I try to run as a GWT app from Eclipse At the moment they are only sucky inconveniences as I'm not using cells that much yet and was able to back them out. And I can still deploy the app via Tomcat and it works. But this is definitely not a reason for the GWT folks to pop open a beer. Konstantin suggested additional dump info. Frankly I've already toasted a day on this and don't have any more time so I'm gonna trudge forward with my workaround. But it's extremely easy to reproduce: Fresh Helios-SR2, 1.6.0_24 jre, fresh install of latest GPE, GWT, and Designer exactly as documented at the site. Fresh brand new boilerplate GreetServlet. Bingo - instant reproduction. Without even touching my Composite. While I'm in a whiny mood, I tried to downgrade to the previous GPE but could not find it. So another question for the GWT folks -- where is it hiding? Or do you suggest doing a full backup of my Eclipse install before a seemingly harmless upgrade to the latest GWT? I backup my Workspace hourly, but usually save the Eclipse install for anticipated big changes. GWT is a GREAT product, please keep it the best of breed it is and treat this as a Priority 1! Thanks, Joe -- 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.
Re: Designer Problems after GWT 2.3 install
Didn't for me. I installed a clean copy of eclipse to c:\eclipse\ andd then installed the gwt plugin 2.3. Same error came up on my test project. -- 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.
Re: Designer Problems after GWT 2.3 install
Please create a bug report from the error window and append it to this case... http://code.google.com/p/google-web-toolkit/issues/detail?id=6316 Also note that this error can occur for other reasons (see earlier in this thread). On May 5, 12:49 pm, Ian Jacobs ian.jac...@gmail.com wrote: Didn't for me. I installed a clean copy of eclipse to c:\eclipse\ andd then installed the gwt plugin 2.3. Same error came up on my test project. -- 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.
Re: Designer Problems after GWT 2.3 install
I take it back. My 1st test was using a gwt plugin I installed into a directory with spaces. I changed the classpath to use the gwt plugin off of c:\eclipse\ and the designer loaded without incident. -- 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.
Re: Designer Problems after GWT 2.3 install
See the latest update to... http://code.google.com/p/google-web-toolkit/issues/detail?id=6316 We hope to have a patch out tomorrow. In the meantime, a work around is available. On May 5, 2:09 pm, Ian Jacobs ian.jac...@gmail.com wrote: I take it back. My 1st test was using a gwt plugin I installed into a directory with spaces. I changed the classpath to use the gwt plugin off of c:\eclipse\ and the designer loaded without incident. -- 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.
Designer Problems after GWT 2.3 install
Hi, I upgraded this AM to 2.3, and have not been able to launch the designer since. I went as far a reinstalling helios-SR2 and reinstalling the latest versions of the plugin and designer. I get this message even with a brand new out of the box web app. I've searched around and can't find any references. Woe is me... Any help would be really appreciated! Thanks, Joe Internal Error GWT Designer encountered unexpected internal error. This could be caused by a GWT Designer bug or by a misconfiguration issue, conflict, partial update, etc. Show stack trace. Hide stack trace. Stack trace: java.lang.NullPointerException at java.io.File.init(Unknown Source) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.getSharedClassLoader(HostedModeSupport.java:225) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.createClassLoaders(HostedModeSupport.java:117) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.init(HostedModeSupport.java:66) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupportFactory.create(HostedModeSupportFactory.java:19) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.getHostedModeSupport(GwtState.java:1188) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize0(GwtState.java:234) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(GwtState.java:210) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFactory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoader(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFactory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(JavaInfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser.java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:404) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:354) at org.eclipse.wb.internal.core.editor.UndoManager.refreshDesignerEditor(UndoManager.java:381) at org.eclipse.wb.internal.core.editor.UndoManager.activate(UndoManager.java:90) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState_True(DesignPage.java:247) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState(DesignPage.java:225) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode.showPage(DefaultMultiMode.java:125) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode$1.widgetSelected(DefaultMultiMode.java:63) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:2743) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1429) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:257) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at
Re: Designer Problems after GWT 2.3 install
Another data point - reverted to GWT 2.2, and seeing a slightly different problem.I also installed the latest plugin this morning. Could the plugin be the problem?? Can't find GWT module GWT Designer can't find GWT module com.google.gwt.user.theme.clean.Clean in project. Possible reasons: 1. There really are no module with this ID. For example, it was just mistyped or accidentally broken. 2. Jar files or project that contains the required module is not included into the classpath of the current GWT project. Show stack trace. Hide stack trace. Stack trace: org.eclipse.wb.internal.core.utils.exception.DesignerException: 4000 (Can't find GWT module). com.google.gwt.user.theme.clean.Clean at org.eclipse.wb.internal.core.utils.check.Assert.isTrueException(Assert.java:388) at com.google.gdt.eclipse.designer.util.ModuleVisitor.accept(ModuleVisitor.java:127) at com.google.gdt.eclipse.designer.util.ModuleVisitor.accept(ModuleVisitor.java:176) at com.google.gdt.eclipse.designer.util.ModuleVisitor.accept(ModuleVisitor.java:101) at com.google.gdt.eclipse.designer.util.Utils.getFileForResource(Utils.java:654) at com.google.gdt.eclipse.designer.util.Utils.getFilesForResources(Utils.java:640) at com.google.gdt.eclipse.designer.util.Utils.getFileForResource(Utils.java:614) at com.google.gdt.eclipse.designer.util.Utils.getHTMLFile_web(Utils.java:1004) at com.google.gdt.eclipse.designer.util.Utils.getHTMLFile(Utils.java:951) at com.google.gdt.eclipse.designer.util.Utils.getDocType(Utils.java:810) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(GwtState.java:163) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFactory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoader(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFactory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(JavaInfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser.java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:404) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:354) at org.eclipse.wb.internal.core.editor.UndoManager.refreshDesignerEditor(UndoManager.java:381) at org.eclipse.wb.internal.core.editor.UndoManager.activate(UndoManager.java:90) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState_True(DesignPage.java:247) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState(DesignPage.java:225) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode.showPage(DefaultMultiMode.java:125) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode$1.widgetSelected(DefaultMultiMode.java:63) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:2743) at
Re: Designer Problems after GWT 2.3 install
I have the same story with the exact same error message (NullPointerException, java.io.File, etc.). I have been banging my head against this one all day with no luck! GWT team please help! - Mike On May 4, 4:45 pm, Joe D. jad...@gmail.com wrote: Hi, I upgraded this AM to 2.3, and have not been able to launch the designer since. I went as far a reinstalling helios-SR2 and reinstalling the latest versions of the plugin and designer. I get this message even with a brand new out of the box web app. I've searched around and can't find any references. Woe is me... Any help would be really appreciated! Thanks, Joe Internal Error GWT Designer encountered unexpected internal error. This could be caused by a GWT Designer bug or by a misconfiguration issue, conflict, partial update, etc. Show stack trace. Hide stack trace. Stack trace: java.lang.NullPointerException at java.io.File.init(Unknown Source) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.getSharedClassLoader(HostedModeSupport.java:225) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.createClassLoaders(HostedModeSupport.java:117) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.init(HostedModeSupport.java:66) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupportFactory.create(HostedModeSupportFactory.java:19) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.getHostedModeSupport(GwtState.java:1188) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize0(GwtState.java:234) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(GwtState.java:210) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFactory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoader(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFactory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(JavaInfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser.java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:404) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:354) at org.eclipse.wb.internal.core.editor.UndoManager.refreshDesignerEditor(UndoManager.java:381) at org.eclipse.wb.internal.core.editor.UndoManager.activate(UndoManager.java:90) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState_True(DesignPage.java:247) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState(DesignPage.java:225) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode.showPage(DefaultMultiMode.java:125) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode$1.widgetSelected(DefaultMultiMode.java:63) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at
Re: Designer Problems after GWT 2.3 install
Please, send error reports (as suggested in error message) instead of just posting stack traces here. Error report includes more context information, including classpath and logs. In this case just stack trace is not very helpful. -- 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.
Re: Designer Problems after GWT 2.3 install
A co-worker and I are having the exact same issue as the original poster in both Eclipse 3.5 and 3.6. I even setup a fresh installation of Eclipse 3.6, downloaded all the plugins, and created an example GWT project and it still didn't work. We have been fighting this all day as well and made no progress. Tim On May 4, 5:07 pm, CTO_Mike michael.daco...@gmail.com wrote: I have the same story with the exact same error message (NullPointerException, java.io.File, etc.). I have been banging my head against this one all day with no luck! GWT team please help! - Mike On May 4, 4:45 pm, Joe D. jad...@gmail.com wrote: Hi, I upgraded this AM to 2.3, and have not been able to launch the designer since. I went as far a reinstalling helios-SR2 and reinstalling the latest versions of the plugin and designer. I get this message even with a brand new out of the box web app. I've searched around and can't find any references. Woe is me... Any help would be really appreciated! Thanks, Joe Internal Error GWT Designer encountered unexpected internal error. This could be caused by a GWT Designer bug or by a misconfiguration issue, conflict, partial update, etc. Show stack trace. Hide stack trace. Stack trace: java.lang.NullPointerException at java.io.File.init(Unknown Source) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.getSharedClassLoader(HostedModeSupport.java:225) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.createClassLoaders(HostedModeSupport.java:117) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupport.init(HostedModeSupport.java:66) at com.google.gdt.eclipse.designer.hosted.tdt.HostedModeSupportFactory.create(HostedModeSupportFactory.java:19) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.getHostedModeSupport(GwtState.java:1188) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize0(GwtState.java:234) at com.google.gdt.eclipse.designer.model.widgets.support.GwtState.initialize(GwtState.java:210) at com.google.gdt.eclipse.designer.parser.ParseFactory.getClassLoader(ParseFactory.java:403) at org.eclipse.wb.internal.core.parser.AbstractParseFactory.initializeClassLoader(AbstractParseFactory.java:732) at com.google.gdt.eclipse.designer.parser.ParseFactory.getRootContext(ParseFactory.java:103) at org.eclipse.wb.internal.core.parser.JavaInfoParser.prepareParseContext(JavaInfoParser.java:1185) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:244) at org.eclipse.wb.internal.core.parser.JavaInfoParser.access$9(JavaInfoParser.java:240) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser$1.runObject(JavaInfoParser.java:1) at org.eclipse.wb.internal.core.utils.execution.ExecutionUtils.runDesignTime(ExecutionUtils.java:153) at org.eclipse.wb.internal.core.parser.JavaInfoParser.parse(JavaInfoParser.java:151) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:463) at org.eclipse.wb.internal.core.editor.DesignPage.access$9(DesignPage.java:455) at org.eclipse.wb.internal.core.editor.DesignPage$7$1.run(DesignPage.java:388) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:179) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150) at org.eclipse.swt.widgets.Display.syncExec(Display.java:4584) at org.eclipse.wb.internal.core.editor.DesignPage$7.run(DesignPage.java:385) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF_withProgress(DesignPage.java:404) at org.eclipse.wb.internal.core.editor.DesignPage.internal_refreshGEF(DesignPage.java:354) at org.eclipse.wb.internal.core.editor.UndoManager.refreshDesignerEditor(UndoManager.java:381) at org.eclipse.wb.internal.core.editor.UndoManager.activate(UndoManager.java:90) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState_True(DesignPage.java:247) at org.eclipse.wb.internal.core.editor.DesignPage.handleActiveState(DesignPage.java:225) at org.eclipse.wb.internal.core.editor.multi.DefaultMultiMode.showPage(DefaultMultiMode.java:125) at
