Ok, I gave it a try. I ran "demo-shell -noserver" and got a pop-up
window with the following msg.
The connection was refused when
attempting to contact localhost:8888.
Without the -noserver I get this.
General Error:
java.lang.NumberFormatException: For input
string: "8888/com.mudd.demo"
Do I need to disable the code that calls my XML/RPC server in order to
run with the -noserver option?
John
On Oct 14, 1:10 pm, "Isaac Truett" <[EMAIL PROTECTED]> wrote:
> The -noserver option lets you debug your GWT client code in hosted mode
> while running any server you like, Tomcat or otherwise.On Tue, Oct 14, 2008
> at 12:58 PM, JohnMudd <[EMAIL PROTECTED]> wrote:
>
> > Running "demo-shell -noserver" doesn't change my situation. I'm using
> > an XML/RPC server, not Tomcat.
>
> > $ demo-shell -?
> > Unknown argument: -?
> > Google Web Toolkit 1.4.62
> > GWTShell [-port port-number | "auto"] [-noserver] [-whitelist
> > whitelist-string] [-blacklist blacklist-string] [-logLevel level] [-
> > gen dir] [-out dir] [-style style] [url]
>
> > where
> > -port Runs an embedded Tomcat instance on the specified port
> > (defaults to 8888)
> > -noserver Prevents the embedded Tomcat server from running, even
> > if a port is specified
> > ...
>
> > On Oct 14, 11:43 am, "Isaac Truett" <[EMAIL PROTECTED]> wrote:
> > > Why can't you run hosted mode with the -noserver option?
>
> > > On Tue, Oct 14, 2008 at 11:38 AM, JohnMudd <[EMAIL PROTECTED]> wrote:
>
> > > > Any way to get the same sort of debugging support in compile mode as
> > > > in shell mode?
>
> > > > I'm using XML/RPC so I have to run in compile mode, not shell mode.
> > > > The biggest drawback is all errors are not caught and reported. That
> > > > turns simple errors into long bug hunts.
>
> > > > I'm running inside a try block now and reporting all exceptions (that
> > > > are caught) in a log panel. That helps but I still run into errors
> > > > that go uncaught, just as trying to use panel object that has been set
> > > > to null. All I get now in unexpected behavior that I have to manually
> > > > track down.
>
> > > > If the problem is just that there's "no place" to report errors in
> > > > compile mode then I'd be happy to provide a panel object where error
> > > > messages can be added.
>
> > > > John
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
