GWT / GXT compilation slow and freezes my Windows ?

Recently I was able to run some basic GWT / GXT compilation tests to compare time efficiency between some old and new machines using Microsoft Windows. Test results wasn’t something that surprised me much but by accident I was able to find a reason that makes GWT compilation choke even modern monster desktops (6 core Phenom 3.3GHz with fast 8GB Dual RAM and top SSD II Disc)

If you are using something else then lightweight anti-virus program your GWT compilation can be much more time consuming (depending on project size and complexity average of few times longer) and even freeze your desktop for a little while.

Suggestion: use lightweight anti-virus program (like Avast AV) or change its configuration that it would skip real time scanning of your local drive (greatly improves compilation time with NOD32, Norton AV etc…)

You May Also Like

Spring Security by example: securing methods

This is a part of a simple Spring Security tutorial:

1. Set up and form authentication
2. User in the backend (getting logged user, authentication, testing)
3. Securing web resources
4. Securing methods
5. OpenID (login via gmail)
6. OAuth2 (login via Facebook)
7. Writing on Facebook wall with Spring Social

Securing web resources is all nice and cool, but in a well designed application it's more natural to secure methods (for example on backend facade or even domain objects). While we may get away with role-based authorization in many intranet business applications, nobody will ever handle assigning roles to users in a public, free to use Internet service. We need authorization based on rules described in our domain.

For example: there is a service AlterStory, that allows cooperative writing of stories, where one user is a director (like a movie director), deciding which chapter proposed by other authors should make it to the final story.

The method for accepting chapters, looks like this:

Read more »