Skip to content
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.

Latest commit

 

History

History
68 lines (56 loc) · 2.88 KB

README.md

File metadata and controls

68 lines (56 loc) · 2.88 KB

spring-security-gwt-template

Spring MVC and Spring Security for the middleware, and Google Web Toolkit for the front-end.

Requires JRE 1.6+ compatible servlet container for running built code

CI Build via BuildHive: spring-security-gwt-template

Development

  1. Download and install the Eclipse IDE. If you have not done so before, I suggest the Eclipse IDE for Java Developers package.
  2. Download and install the Google Plugin for Eclipse. More detailed instructions for installation on Eclipse 4.2.
  3. Right-Click OR CMD-Click on the build.xml file and hit Run As -> Ant Build ....
  4. Select the clean and eclipse-dev Ant build targets, so that the target execution order looks like clean, eclipse-dev. Next, launch with the GWT_Debug.launch config for debugging server and front-end code. OR. Use the clean and (default) gwt-dev Ant targets to allow Ant to handle the entire launch, but you won't be able to debug server-side code.
  5. Click Launch Default Browser or select a launch URL. You may need to fiddle with the devmode permissions when on Windows.
  6. Proceed with the plugin setup, restart browser, and enjoy coding!

FAQ

Q: What does GWT module 'com.vraidsys.MainEntryPoint' may need to be (re)compiled mean?

A: As currently configured, Spring auto-redirects all requests from a user that is not authenticated to /login.html. In GWT devmode, on-the-fly compilation of Java to JavaScript is served up to the browser based on the ?gwt.codesvr= URL parameter. Thus, when Spring auto-redirects, this parameter is lost and the browser does not know where to pull its instructions from.

The two part process when working in devmode:

  1. log in when prompted, which will set the appropriate auth cookies
  2. click the devmode console "launch browser" button again

License