Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
The error is self described: Missing required argument 'module[s]. You have to add the module(s) On 24 February 2015 at 16:33, ssg shivag...@gmail.com wrote: 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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe 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]superDevModeRuns 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 -modulePathPrefixThe 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. On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote: On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote: 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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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. On Tuesday, February 24, 2015 at 2:46:21 PM UTC-5, Juan Pablo Gardella wrote: The error is self described: Missing required argument 'module[s]. You have to add the module(s) On 24 February 2015 at 16:33, ssg shiv...@gmail.com javascript: wrote: 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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe 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]superDevModeRuns 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 -modulePathPrefixThe 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. On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote: On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote: 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) -portSpecifies the TCP port for the embedded web server
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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. On Tuesday, February 24, 2015 at 9:52:24 AM UTC-5, Jens wrote: Instead of GWTShell use com.google.gwt.dev.DevMode -- J. -- 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/d/optout.
Re: GWT Dagger 2
Jens thank you for your reply. What's the best way to include your PR ( https://github.com/google/dagger/pull/119) in a project? On Tuesday, February 24, 2015 at 1:54:57 PM UTC, Jens wrote: You need to add the generated sources as Eclipse source folder to make them usable in Eclipse, e.g.: http://stackoverflow.com/questions/7160006/m2e-and-having-maven-generated-source-folders-as-eclipse-source-folders Maybe the above also fixes the gwt:compile class path issue. For successful GWT compilation you also need Dagger + javax.inject sources and a GWT module to make them available to GWT compiler. I have done an initial pull request for Dagger to simplify that in the future: https://github.com/google/dagger/pull/119 -- J. -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
Instead of GWTShell use com.google.gwt.dev.DevMode -- J. -- 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/d/optout.
Re: CellList inside a panel of 100% height
table.setHeight(String.valueOf(Window.getClientHeight() - (the amount of px you want to leave from top)) + Unit.PX); Thanks, Tushar On Monday, February 23, 2015 at 8:48:34 AM UTC+5:30, Magnus wrote: Hi, consider the CellList example in GWT showcase: http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellList The CellList in this example has a fixed height of 400 px. If you change it to 100%, the scrollbars are gone! (You can verify this right in the showcase example.). However, I would like it to fill the whole height. What can I do? Thanks Magnus -- 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/d/optout.
Re: Grouping in GWT Celltable?
I think I did something similar in past. It was sort of a hack. I had all the data sorted from backend. While defining the columns in frontend, I would compare current data to previous data (store in a member variable). If both are same, don't set any data in the cell. It sort of gives an appearance of data being grouped. Thanks, Tushar On Monday, February 23, 2015 at 4:17:17 PM UTC+5:30, Mohammed wrote: Hi, I need grouping in gwt celltable,Is it possible to have grouping on celltable?Any example ,suggestion? -- 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/d/optout.
Re: GWT Dagger 2
What's the best way to include your PR ( https://github.com/google/dagger/pull/119) in a project? Its a branch in my dagger fork that you can simply build and install into your local repo: https://github.com/jnehlmeier/dagger/tree/gwt-integration -- J. -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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. -- 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/d/optout.
Re: GWT Dagger 2
Errata:
The project class paths that are included in GWT compile command are:
/path/to/project/target/tmp/WEB-INF/classes
*/path/to/project/src/main/java*
On Tuesday, February 24, 2015 at 1:29:17 PM UTC, Vasco Andrade Silva wrote:
Hi all,
I've been trying Dagger 2 with GWT and have been fighting to get things
working. Could someone help?
My pom:
dependency
groupIdcom.google.dagger/groupId
artifactIddagger/artifactId
version2.0-SNAPSHOT/version
/dependency
dependency
groupIdcom.google.dagger/groupId
artifactIddagger-compiler/artifactId
version2.0-SNAPSHOT/version
optionaltrue/optional
/dependency
[...]
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdgwt-maven-plugin/artifactId
version${gwtVersion}/version
executions
execution
goals
goalcompile/goal
goaltest/goal
/goals
/execution
/executions
configuration
modulemy.Module/module
extraJvmArgs-Xmx2048M -XX:MaxPermSize=128M/extraJvmArgs
runTargetindex.html/runTarget
warSourceDirectory${project.build.directory}/${tmpTargetDirectory}
/warSourceDirectory
buildOutputDirectory
${project.build.directory}/${tmpTargetDirectory}/WEB-INF/classes/
/buildOutputDirectory
hostedWebapp${project.build.directory}/${tmpTargetDirectory}
/hostedWebapp
webappDirectory${project.build.directory}/${tmpTargetDirectory}
/webappDirectory
webXml${project.build.directory}/${tmpTargetDirectory}/WEB-INF/webXml
generateDirectorysrc/main/java/generateDirectory
bindAddress0.0.0.0/bindAddress
jsInteropModeJS/jsInteropMode
closureCompilertrue/closureCompiler
/configuration
/plugin
My issues are:
*#1 generated sources aren't available for gwt compilation*
running:
mvn compile
no errors are found in the compilation phase, dagger 2 generated sources
land in *target/generated-sources/annotations/*
However running:
mvn compile gwt:compile
GWT compilation outputs the following error:
[ERROR] Errors in
'file:/path/to/project/src/main/java/path/to/project/client/ProjectEntryPoint.java'
[INFO] [ERROR] Line 79: No source code is available for type path.to.
project.client.Dagger_ProjectComponent; did you forget to inherit a
required module?
[INFO] [ERROR] Hint: Check the inheritance chain from your module; it may
not be inheriting a required module or a module may not be adding its
source path entries properly
the problem seems related with the fact that GWT compilation isn't
including the generated sources, as target/generated-sources/annotations/
isn't included in the classpath of the GWT compiler. The project class
paths that are included in GWT compile command are:
/path/to/project/target/tmp/WEB-INF/classes
/path/to/project/target/src/main/java
*#2 Eclipse doesn't follow Dagger 2 generate sources (not related with
GWT per-si)*
I configured Eclipse (Luna edition) with m2e-apt plugin (
http://marketplace.eclipse.org/content/m2e-apt). My project works as a
maven project in Eclipse.
However when I change something in dagger (Component, Module, etc.) the
generated sources aren't immediately generated, I need to do Maven
Update Project.
*#3 Eclipse imports errors on Dagger 2 generated files open **(not
related with GWT per-si)*
When I open a file that was generated by dagger 2 (in
target/generated/sources/annotations) eclipse doesn't know how to import
other sources from target/generated/sources/annotations which lead to
several compile time errors in those generated files. Additionally, from
that point on Eclipse confuses himself and makes the project source files
(in src/main/java) that are referring to generated dagger files
(e.g. Dagger_ProjectComponent) to also be in error (eclipse doesn't know
anymore to import those symbols).
To overcome this I have to do Maven Update Project. Note, however,
that every time I open a dagger2 generated file, this happens again.
--
Has someone succeeded getting dagger 2 and GWT (and Eclipse) working
together smoothly?
Also, any help to overcome the reported issues would be great (specially
issue #1).
Thank you,
Vasco
--
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/d/optout.
Re: GWT Dagger 2
You need to add the generated sources as Eclipse source folder to make them usable in Eclipse, e.g.: http://stackoverflow.com/questions/7160006/m2e-and-having-maven-generated-source-folders-as-eclipse-source-folders Maybe the above also fixes the gwt:compile class path issue. For successful GWT compilation you also need Dagger + javax.inject sources and a GWT module to make them available to GWT compiler. I have done an initial pull request for Dagger to simplify that in the future: https://github.com/google/dagger/pull/119 -- J. -- 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/d/optout.
launchConfiguration issue for GWT 2.7.0 (New to GWT)
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.0quot; encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry containerPath=quot;org.eclipse.jdt.launching.JRE_CONTAINERquot; javaProject=quot;MmseaAppquot; path=quot;1quot; type=quot;4quot;/gt;#13;#10;/ listEntry value=lt;?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry internalArchive=quot;/MmseaApp/srcquot; path=quot;3quot; type=quot;2quot;/gt;#13;#10;/ listEntry value=lt;?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry id=quot;org.eclipse.jdt.launching.classpathentry.defaultClasspathquot;gt;#13;#10;lt;memento project=quot;MmseaAppquot;/gt;#13;#10;lt;/runtimeClasspathEntrygt;#13;#10;/ listEntry value=lt;?xml version=quot;1.0quot; encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry externalArchive=quot;C:/gwt 1.7.0/gwt-windows-1.7.0/gwt-dev-windows.jarquot; path=quot;3quot; type=quot;2quot;/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. -- 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/d/optout.
GWT Dagger 2
Hi all,
I've been trying Dagger 2 with GWT and have been fighting to get things
working. Could someone help?
My pom:
dependency
groupIdcom.google.dagger/groupId
artifactIddagger/artifactId
version2.0-SNAPSHOT/version
/dependency
dependency
groupIdcom.google.dagger/groupId
artifactIddagger-compiler/artifactId
version2.0-SNAPSHOT/version
optionaltrue/optional
/dependency
[...]
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdgwt-maven-plugin/artifactId
version${gwtVersion}/version
executions
execution
goals
goalcompile/goal
goaltest/goal
/goals
/execution
/executions
configuration
modulemy.Module/module
extraJvmArgs-Xmx2048M -XX:MaxPermSize=128M/extraJvmArgs
runTargetindex.html/runTarget
warSourceDirectory${project.build.directory}/${tmpTargetDirectory}
/warSourceDirectory
buildOutputDirectory
${project.build.directory}/${tmpTargetDirectory}/WEB-INF/classes/
/buildOutputDirectory
hostedWebapp${project.build.directory}/${tmpTargetDirectory}
/hostedWebapp
webappDirectory${project.build.directory}/${tmpTargetDirectory}
/webappDirectory
webXml${project.build.directory}/${tmpTargetDirectory}/WEB-INF/webXml
generateDirectorysrc/main/java/generateDirectory
bindAddress0.0.0.0/bindAddress
jsInteropModeJS/jsInteropMode
closureCompilertrue/closureCompiler
/configuration
/plugin
My issues are:
*#1 generated sources aren't available for gwt compilation*
running:
mvn compile
no errors are found in the compilation phase, dagger 2 generated sources
land in *target/generated-sources/annotations/*
However running:
mvn compile gwt:compile
GWT compilation outputs the following error:
[ERROR] Errors in
'file:/path/to/project/src/main/java/path/to/project/client/ProjectEntryPoint.java'
[INFO] [ERROR] Line 79: No source code is available for type path.to.project
.client.Dagger_ProjectComponent; did you forget to inherit a required module
?
[INFO] [ERROR] Hint: Check the inheritance chain from your module; it may
not be inheriting a required module or a module may not be adding its
source path entries properly
the problem seems related with the fact that GWT compilation isn't
including the generated sources, as target/generated-sources/annotations/
isn't included in the classpath of the GWT compiler. The project class
paths that are included in GWT compile command are:
/path/to/project/target/tmp/WEB-INF/classes
/path/to/project/target/src/main/java
*#2 Eclipse doesn't follow Dagger 2 generate sources (not related with
GWT per-si)*
I configured Eclipse (Luna edition) with m2e-apt plugin
(http://marketplace.eclipse.org/content/m2e-apt). My project works as a
maven project in Eclipse.
However when I change something in dagger (Component, Module, etc.) the
generated sources aren't immediately generated, I need to do Maven
Update Project.
*#3 Eclipse imports errors on Dagger 2 generated files open **(not related
with GWT per-si)*
When I open a file that was generated by dagger 2 (in
target/generated/sources/annotations) eclipse doesn't know how to import
other sources from target/generated/sources/annotations which lead to
several compile time errors in those generated files. Additionally, from
that point on Eclipse confuses himself and makes the project source files
(in src/main/java) that are referring to generated dagger files
(e.g. Dagger_ProjectComponent) to also be in error (eclipse doesn't know
anymore to import those symbols).
To overcome this I have to do Maven Update Project. Note, however, that
every time I open a dagger2 generated file, this happens again.
--
Has someone succeeded getting dagger 2 and GWT (and Eclipse) working
together smoothly?
Also, any help to overcome the reported issues would be great (specially
issue #1).
Thank you,
Vasco
--
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/d/optout.
Re: Static vs dynamic String internationalization
That, of course, depends on the application requirement. I work on a very large app which is not (only) used by ourselves, but by other organizations. And on each organization, administrators can change translations on the fly - just a F5 or logout / login away. In this scenario, of course, there is no choice. We even created a custom translations loading mechanism that efficiently use the browser cache and load translations in parts, as there are more than 4k keys, as we don't want all them to be always downloaded. Each page (it all started in GWT 1.5, before GWT places existed) knows which translation part it needs, so we guarantee to load the required translations before showing the page. But, I agree, it is a very specific requirement. Maybe 99% of the applications are fine with static internationalization. We're part of the other 1%. -- Luis Em segunda-feira, 23 de fevereiro de 2015 19:33:34 UTC-3, Jens escreveu: - The big advantage of dynamic internationalization to me, is that I can store my translations in a database, and update texts without the need of stopping servers to deploy a new compiled version of my application. Not sure if its that big of an advantage. IMHO translations rarely change and the number of supported languages is probably already known upfront and does not change often either. Also if done right, updating an app does not cause any downtime especially if only translations have changed or languages have been added. The worst case is that a user gets a message App has been updated and needs to be reloaded. If your app uses history tokens (e.g. GWT places) then reloading the current place doesn't really hurt. -- J. -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe 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]superDevModeRuns 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 -modulePathPrefixThe 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. On Tuesday, February 24, 2015 at 10:39:30 AM UTC-5, Jens wrote: 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. -- 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/d/optout.
Re: GWT Dagger 2
On Tuesday, February 24, 2015 at 2:29:17 PM UTC+1, Vasco Andrade Silva wrote: My issues are: *#1 generated sources aren't available for gwt compilation* running: mvn compile no errors are found in the compilation phase, dagger 2 generated sources land in *target/generated-sources/annotations/* However running: mvn compile gwt:compile GWT compilation outputs the following error: [ERROR] Errors in 'file:/path/to/project/src/main/java/path/to/project/client/ProjectEntryPoint.java' [INFO] [ERROR] Line 79: No source code is available for type path.to. project.client.Dagger_ProjectComponent; did you forget to inherit a required module? [INFO] [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly the problem seems related with the fact that GWT compilation isn't including the generated sources, as target/generated-sources/annotations/ isn't included in the classpath of the GWT compiler. The project class paths that are included in GWT compile command are: /path/to/project/target/tmp/WEB-INF/classes /path/to/project/target/src/main/java Which version of the maven-compiler-plugin are you using? m-compiler-p didn't add the generated-sources to the compileSourceRoots until version 3.2: https://jira.codehaus.org/browse/MCOMPILER-157, so you had to use the build-helper-maven-plugin to add it. -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote: 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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe 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]superDevModeRuns 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 -modulePathPrefixThe 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. 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) -- 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/d/optout.
Re: GWT 2.7/GwtMockito: History support
Hi, Thanks for your answer. I'll look into putting a layer between GWT (at least the parts that use static helpers) and our application code then. For now the ugliness works, and I guess I'll be able to use it also in similar other situations. Regards, -- Andreas On Tuesday, February 17, 2015 at 11:19:54 AM UTC+1, Jens wrote: is there any specific reason not to make HistoryImpl accessible? Its good practice for a library to hide implementation details because you do not want developers to accidentally or knowingly depend on these details. I am pretty sure other features of GwtMockito look equally ugly, because GwtMockito itself is a huge hack to circumvent GWT.create() and JSNI in unit tests. Often you can also just refactor your app a bit so it does not directly call such GWT methods. You can wrap them in helper classes like HistoryTokenEncoder that you can swap out during testing or wrap them using a helper method that can be overwritten in tests (anonymously or by sub classing) -- J. -- 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/d/optout.
(Server-side) AutoBeans and thread-safety
Hi,
I hope this is the right forum to also ask questions about the Autobeans
framework, if not please do redirect me!
We're using autobeans both in client code and server code, and so far
things work nicely except in one situation: sometimes parsing autobeans
simply fails with a stack trace similar to this:
java.lang.NullPointerException
at com.google.web.bindery.autobean.vm.impl.ProxyAutoBean.makeProxy(
ProxyAutoBean.java:105)
at com.google.web.bindery.autobean.vm.impl.ProxyAutoBean.createShim(
ProxyAutoBean.java:393)
at com.google.web.bindery.autobean.vm.impl.ProxyAutoBean.as(ProxyAutoBean.
java:222)
at com.google.web.bindery.autobean.vm.impl.ShimHandler.maybeWrap(ShimHandler
.java:113)
at com.google.web.bindery.autobean.vm.impl.ShimHandler.invoke(ShimHandler.
java:91)
at com.sun.proxy.$Proxy368.get(Unknown Source)
at com.google.web.bindery.autobean.shared.impl.SplittableSimpleMap$1$1$1.
init(SplittableSimpleMap.java:90)
at com.google.web.bindery.autobean.shared.impl.SplittableSimpleMap$1$1.next(
SplittableSimpleMap.java:86)
at com.google.web.bindery.autobean.shared.impl.SplittableSimpleMap$1$1.next(
SplittableSimpleMap.java:76)
at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.google.web.bindery.autobean.vm.impl.ShimHandler.invoke(ShimHandler.
java:85)
at com.sun.proxy.$Proxy347.next(Unknown Source)
at XXX.function(XXX.java:...)
When dumping the contents of the bean at that point everything looks
proper, and it can be parsed just fine in an isolated unit test. After some
more investigation I managed to reproduce this and other similar
exceptions: it seems to happen when multiple threads access a recently
created autobean proxy.
I understand that autobean's are actually parsed lazily, so for me this
looks like a concurrency issue somewhere inside the autobeans framework
itself. I didn't see any notes about sharing autobeans between threads in
the documentation, so:
1. Should it be possible to share them, or is additional synchronization in
the application code needed?
2. Instead of synchronizing all accesses, would it be enough to force a
full parse run of the autobean before making it visible to other threads?
3. Is this problem only affecting server-side code, or would similar issues
also be possible in client-side code? (I'm suspecting: It depends on the
browser's implementation of JS?)
Regarding the second question: I did not manage to reproduce the issue by
using this additional code:
AutoBeanUtils.getAutoBean(delegate).accept(new AutoBeanVisitor() { /*
Nothing */ });
Regards,
--
Andreas
--
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/d/optout.
JSONPath
Hello. Does anyone know a GWT library that supports JSONPath queries at runtime? I don't know the desired JSONPath expression at compile time (it's a configuration kept on the server), so i think any solution relying on GWT generators doesn't fit my use case. Thank you, Nuno -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe 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]superDevModeRuns 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 -modulePathPrefixThe 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. On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote: On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote: 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) -portSpecifies the TCP port for the embedded web server (defaults to ) -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 -logLevelThe level of logging detail: ERROR, WARN, INFO, TRACE, DEBUG, SPAM, or ALL -gen
Re: Grouping in GWT Celltable?
Can you please give me an example code for celltable grouping? On Monday, February 23, 2015 at 4:17:17 PM UTC+5:30, Mohammed wrote: Hi, I need grouping in gwt celltable,Is it possible to have grouping on celltable?Any example ,suggestion? -- 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/d/optout.
Re: GWT Dagger 2
Thank you Thomas and Jens. Thomas, I was using v. 2.3.2 for maven-compiler-plugin, upgraded to 3.2 and everything worked without build-helper-maven-plugin as you described - thanks! Jens, I did as you said and everything worked! I Hope that the Dagger 2 team merge your PR asap - thank you! I couldn't make Eclipse work as good as it should (still have issues #2 and #3) and I'm still relying on Maven Update Project - I'll deep dive in https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html and see if I can make any progress. On Tuesday, February 24, 2015 at 5:07:04 PM UTC, Thomas Broyer wrote: On Tuesday, February 24, 2015 at 2:29:17 PM UTC+1, Vasco Andrade Silva wrote: My issues are: *#1 generated sources aren't available for gwt compilation* running: mvn compile no errors are found in the compilation phase, dagger 2 generated sources land in *target/generated-sources/annotations/* However running: mvn compile gwt:compile GWT compilation outputs the following error: [ERROR] Errors in 'file:/path/to/project/src/main/java/path/to/project/client/ProjectEntryPoint.java' [INFO] [ERROR] Line 79: No source code is available for type path.to. project.client.Dagger_ProjectComponent; did you forget to inherit a required module? [INFO] [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly the problem seems related with the fact that GWT compilation isn't including the generated sources, as target/generated-sources/annotations/ isn't included in the classpath of the GWT compiler. The project class paths that are included in GWT compile command are: /path/to/project/target/tmp/WEB-INF/classes /path/to/project/target/src/main/java Which version of the maven-compiler-plugin are you using? m-compiler-p didn't add the generated-sources to the compileSourceRoots until version 3.2: https://jira.codehaus.org/browse/MCOMPILER-157, so you had to use the build-helper-maven-plugin to add it. -- 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/d/optout.
Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)
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/
On 24 February 2015 at 17:47, ssg shivag...@gmail.com wrote:
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.
On Tuesday, February 24, 2015 at 2:46:21 PM UTC-5, Juan Pablo Gardella
wrote:
The error is self described: Missing required argument 'module[s]. You
have to add the module(s)
On 24 February 2015 at 16:33, ssg shiv...@gmail.com wrote:
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)
-portSpecifies the TCP port for the embedded web
server (defaults to )
-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
-logLevelThe 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]superDevModeRuns 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
-modulePathPrefixThe 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.
On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote:
On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote:
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 |
GWT 2.7 Window Close Handle Bug?
Hello,
Since I upgraded to GWT 2.7 my window close handler has stopped working.
Before I submitted a bug report I wanted to see if anybody else was having
this issue and to verify that nothing has changed and I was still doing it
right. My code is:
import com.google.gwt.core.client.EntryPoint;
import com.google.gwt.event.logical.shared.CloseEvent;
import com.google.gwt.event.logical.shared.CloseHandler;
import com.google.gwt.user.client.Window;
public class MyClass implements EntryPoint {
public void onModuleLoad() {
Session session = new Session();
...
Window.addWindowClosingHandler(new Window.ClosingHandler() {
@Override public void onWindowClosing(Window.ClosingEvent event) {
session.reset();
}
});
Window.addCloseHandler(new CloseHandlerWindow() {
@Override public void onClose(CloseEventWindow event) {
session.reset();
}
});
}
I have tried and failed to do the above using JSNI, so bonus points if
anybody can give me an example on how to do it that way as a backup. I
REALLY need to get this working again because the users never use the
logout button and close the browser instead. If I can't resolve the issue
soon I'm going to have to downgrade to GWT 2.6.
James
--
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/d/optout.
