launchConfiguration issue for GWT 2.7.0 (New to GWT)

[ssg]

I am migrating from GWT 1.7.0 to GWT 2.7.0

My GWT 1.7.0 launch configuration ( from MmseaApp.launch file)

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
<listEntry value="/MmseaApp"/>
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="4"/>
</listAttribute>
<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables" value="true"/>
<listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#13;&#10;&lt;runtimeClasspathEntry containerPath=&quot;org.eclipse.jdt.launching.JRE_CONTAINER&quot; javaProject=&quot;MmseaApp&quot; path=&quot;1&quot; type=&quot;4&quot;/&gt;&#13;&#10;"/>
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#13;&#10;&lt;runtimeClasspathEntry internalArchive=&quot;/MmseaApp/src&quot; path=&quot;3&quot; type=&quot;2&quot;/&gt;&#13;&#10;"/>
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#13;&#10;&lt;runtimeClasspathEntry id=&quot;org.eclipse.jdt.launching.classpathentry.defaultClasspath&quot;&gt;&#13;&#10;&lt;memento project=&quot;MmseaApp&quot;/&gt;&#13;&#10;&lt;/runtimeClasspathEntry&gt;&#13;&#10;"/>
<listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#13;&#10;&lt;runtimeClasspathEntry externalArchive=&quot;C:/gwt 1.7.0/gwt-windows-1.7.0/gwt-dev-windows.jar&quot; path=&quot;3&quot; type=&quot;2&quot;/&gt;&#13;&#10;"/>
</listAttribute>
<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="false"/>

<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="com.google.gwt.dev.GWTShell"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-out www mmsea/app.jsp&#10;-noserver&#10;-port 9080"/>

<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="MmseaApp"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xmx256M"/>
</launchConfiguration>

I need help in rewriting/changing the above 2 lines in red text for migrating to GWT 2.7.0 ;

Below are the errors I am getting;

1. Exception in thread "main" java.lang.NoClassDefFoundError: com.google.gwt.dev.GWTShell
   Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.GWTShell
       at java.net.URLClassLoader.findClass(URLClassLoader.java:423)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:660)
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:346)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:626)
2. Unknown argument: -out

Looks like 'com.google.gwt.dev.GWTShell' is deprecated. What is the replacement code for this in GWT 2.7.0 ?

Any help would be greatly appreciated.

Thanks a lot in advance.

[Jens]

Instead of GWTShell use com.google.gwt.dev.DevMode

-- J.

[ssg]

Thanks Jens. I still have the 2nd error "Unknown argument: -out"

How can I rewrite the 2nd line in red text above for GWT 2.7.0. Copying the line here again.

<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-out www mmsea/app.jsp&#10;-noserver&#10;-port 9080"/>

Please let me know. Thanks.

[Jens]

Thanks Jens. I still have the 2nd error "Unknown argument: -out"

 

The DevMode class should show you all valid arguments and the description should tell you which one to choose as a replacement. I don't know anything about GWT 1.7, but I assume DevMode -war is probably the same as GWTShell -out.

-- J.

[ssg]

Jens,

Below is the message I am getting. Not sure which one to use or how to use.

Unknown argument: -out
Google Web Toolkit 2.7.0
DevMode [-[no]startServer] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort port-number | "auto"] [-[no]superDevMode] [-server servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] [-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s]

where
  -[no]startServer         Starts a servlet container serving the directory specified by the -war flag. (defaults to ON)
  -port                    Specifies the TCP port for the embedded web server (defaults to 8888)
  -whitelist               Allows the user to browse URLs that match the specified regexes (comma or space separated)
  -blacklist               Prevents the user browsing URLs that match the specified regexes (comma or space separated)
  -logdir                  Logs to a file in the given directory, as well as graphically
  -logLevel                The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
  -gen                     Debugging: causes normally-transient generated types to be saved in the specified directory
  -bindAddress             Specifies the bind address for the code server and web server (defaults to 127.0.0.1)
  -codeServerPort          Specifies the TCP port for the code server (defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
  -[no]superDevMode        Runs Super Dev Mode instead of classic Development Mode. (defaults to ON)
  -server                  Specify a different embedded web server to run (must implement ServletContainerLauncher)
  -startupUrl              Automatically launches the specified URL
  -war                     The directory into which deployable output files will be written (defaults to 'war')
  -deploy                  The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
  -extra                   The directory into which extra files, not intended for deployment, will be written
  -modulePathPrefix        The subdirectory inside the war dir where DevMode will create module directories. (defaults empty for top level)
  -workDir                 The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
  -XmethodNameDisplayMode  Emit extra information allow chrome dev tools to display Java identifiers in many places instead of JavaScript functions.
  -sourceLevel             Specifies Java source level (defaults to auto:1.6)
  -XjsInteropMode          Specifies JsInterop mode, either NONE, JS, or CLOSURE (defaults to NONE)
  -[no]incremental         Compiles faster by reusing data from the previous compile. (defaults to ON)
and
  module[s]                Specifies the name(s) of the module(s) to host


Can you please help me in rewriting this line based on the above suggestions ?

<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-out www mmsea/app.jsp&#10;-noserver&#10;-port 9080"/>

Thanks a lot.

[Thomas Broyer]

It's been way too long since I used GWTShell (like most of us), but I'd say "-war www -startupUrl mmsea/app.jsp -noserver -port 9080"

Note sure that a relative path as -startupUrl would work well with -noserver though… (and -port is kind of useless with -noserver)

[ssg]

Thanks Thomas. I tried your suggestion as below.
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-war www -startupUrl mmsea/app.jsp -noserver -port 9080"/>

I am getting the following error now;

Missing required argument 'module[s]'

Google Web Toolkit 2.7.0
DevMode [-[no]startServer] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir directory] [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] [-codeServerPort port-number | "auto"] [-[no]superDevMode] [-server servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] [-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s]

where

  -[no]startServer         Starts a servlet container serving the directory specified by the -war flag. (defaults to OFF)

  -port                    Specifies the TCP port for the embedded web server (defaults to 8888)
  -whitelist               Allows the user to browse URLs that match the specified regexes (comma or space separated)
  -blacklist               Prevents the user browsing URLs that match the specified regexes (comma or space separated)
  -logdir                  Logs to a file in the given directory, as well as graphically
  -logLevel                The level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL
  -gen                     Debugging: causes normally-transient generated types to be saved in the specified directory
  -bindAddress             Specifies the bind address for the code server and web server (defaults to 127.0.0.1)
  -codeServerPort          Specifies the TCP port for the code server (defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
  -[no]superDevMode        Runs Super Dev Mode instead of classic Development Mode. (defaults to ON)
  -server                  Specify a different embedded web server to run (must implement ServletContainerLauncher)
  -startupUrl              Automatically launches the specified URL
  -war                     The directory into which deployable output files will be written (defaults to 'war')
  -deploy                  The directory into which deployable but not servable output files will be written (defaults to 'WEB-INF/deploy' under the -war directory/jar, and may be the same as the -extra directory/jar)
  -extra                   The directory into which extra files, not intended for deployment, will be written
  -modulePathPrefix        The subdirectory inside the war dir where DevMode will create module directories. (defaults empty for top level)
  -workDir                 The compiler's working directory for internal use (must be writeable; defaults to a system temp dir)
  -XmethodNameDisplayMode  Emit extra information allow chrome dev tools to display Java identifiers in many places instead of JavaScript functions.
  -sourceLevel             Specifies Java source level (defaults to auto:1.6)
  -XjsInteropMode          Specifies JsInterop mode, either NONE, JS, or CLOSURE (defaults to NONE)
  -[no]incremental         Compiles faster by reusing data from the previous compile. (defaults to ON)
and
  module[s]                Specifies the name(s) of the module(s) to host

Please let me know.

Thanks a lot in advance.

[Juan Pablo Gardella]

The error is self described: "Missing required argument 'module[s]". You have to add the module(s)

--
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-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ssg]

Yes I agree that the error is self explanatory. I was expecting an example code using this argument. Can you please provide me an example ?

Thanks a lot in advance.

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsub...@googlegroups.com.

[Juan Pablo Gardella]

Sure.  (working for GWT 2.7)

<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="com.google.gwt.dev.DevMode"/>

<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-remoteUI &quot;${gwt_remote_ui_server_port}:${unique_id}&quot; -codeServerPort 9997 -port auto -superDevMode -logLevel INFO com.foo.SismuEntryPoint"/>

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.

[ssg]

Juan,
Thanks for the reply. As I am new to GWT I do not understand the PROGRAM_ARGUMENTS" values you mentioned here. Also I do not see a module[s] argument in your example. Based on my code provided earlier , Can you please help me rewrite PROGRAM_ARGUMENTS" values using my code including the module[s] argument as well.

Thanks in advance.

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.

To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Juan Pablo Gardella]

Which is the file where you define your module? For example if it's com/foo/Mymodule.gwt.xml you have to configure your launcher like this:

<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-remoteUI &quot;${gwt_remote_ui_server_port}:${unique_id}&quot; -codeServerPort 9997 -port auto -superDevMode -logLevel INFO com.foo.Mymodule"/>

You can use the eclipse wizard to configure this. Go to Run -> Run configurations -> Web Application. 

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.