Re: Designer Problems after GWT 2.3 install

2011-05-05 Thread Joe D.
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

2011-05-04 Thread Joe D.
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 org.

Designer Problems after GWT 2.3 install

2011-05-04 Thread Joe D.
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.(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.(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 org.eclipse.swt.widgets.Widget.

Re: Problems with Godaddy hosting and server-side deserialization

2011-05-03 Thread Joe D.
Thanks Alan for the lead! I'll check 'em out
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: Problems with Godaddy hosting and server-side deserialization

2011-05-02 Thread Joe D.
Alan,
Do you have suggestions for hosting providers that you are happy with. I'm 
so sick of NoDaddy and trying to fit a square peg (eg GWT) into a round hole 
(eg CrapDaddy). 
*Webhostingjava.net *looks interesting.

There's of course the appengine route, but wouldn't I have to covert my 
existing relational data models to it's object model? Not quite ready for 
that yet.

I've also considered moving away from GWT-RPC to JSON, as the former seems 
to be the problem (if you will). Besides, GWT-RPC is not available for 
Android which is a severe limitation.

Without further babble: decisions, decisions. 

Any wisdom from this awesome GWTer community is truly appreciated!
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.