DDevelopment & Design

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…)

— Previous article

GWT exception in Hosted Mode

Next article —

Sorting strings in Oracle by national rules

You May Also Like
DDevelopment & Design

Grails with Spock unit test + IntelliJ IDEA = No thread-bound request found

During my work with Grails project using Spock test in IntelliJ IDEA I've encountered this error:

java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
 at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.currentRequestAttributes(CommonWebApi.java:205)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.getParams(CommonWebApi.java:65)
... // and few more lines of stacktrace ;)

It occurred when I tried to debug one of test from IDEA level. What is interesting, this error does not happen when I'm running all test using grails test-app for instance.

So what was the issue? With little of reading and tip from Tomek Kalkosiński (http://refaktor.blogspot.com/) it turned out that our test was missing @TestFor annotation and adding it solved all problems.

This annotation, according to Grails docs (link), indicates Spock what class is being tested and implicitly creates field with given type in test class. It is somehow strange as problematic test had explicitly and "manually" created field with proper controller type. Maybe there is a problem with mocking servlet requests?
DDevelopment & Design

Rapid js + css development

BackgroundLast time I had some work to do in OSGi web module written in Spring MVC. If we have application splitted to well-designed modules, back-end development in this framework run in OSGi environment is quite fast because after some modification w...