Last updated by 4 years ago
Page: GWT Release Notes, Version:5
Previously, the security fix was mentioned for version 0.4. Due to human error, the fix wasn't in that release. It is in this one.
- Fixed a security issue that meant clients could invoke methods on any Spring bean in the application. Requests are now only processed if the bean has an "expose" property configured for GWT.
gwt-user.jarfiles are no longer included in the application's WAR.
- GWT RPC calls now go through a Grails controller. This means that the standard Grails filters and interceptors are invoked and also that you can change the URL mappings for GWT requests. Just map your preferred URL to controller "gwt", action "index".
- Added the create-gwt-i18n command, which creates GWT Constants and Messages properties files for a given module.
- There is now a new command, clean-gwt-modules, for cleaning all the generated GWT files.
- The plugin now supports GWT 1.6 and 1.7 without relying on legacy mode.
- The generate-gwt-rpc command now ignores services that aren't exposed via GWT (GRAILSPLUGINS-1215).
- The plugin now uses the GWT libraries from
GWT_HOMEinstead of packaging the JARs itself. This should mean that plugin will work with multiple versions of GWT (including 1.5.x).
- The plugin is Grails 1.1+ only.
- Modules and associated GWT Java files are now located under
src/java. The RPC interfaces still go under
- Automatic generation of RPC interfaces has been removed. Instead, you can manually create them using the new
- Fixed some issues with the RPC handling, particularly with regard to exceptions.
grails cleanremoves directories and directories and files generated by GWT.
- Other JIRA fixes.