DDevelopment & Design

GWTaculous – visual effects on the loose !

GWTaculous is open source visual effects library for application created in or based on GWT. It is based on other open source library –

scriptaculous which is javascript solution for visual effects and html object manipulations. At the first glance GWTaculous is a java wrapper for javascript functions (JSNI) in scriptaculous library. But in fact it is complete solution with full java API (visual effects, effect queues, animation GWT event handlers etc). Let alone documentation and use examples. It also contains some minor bug fixes and will be updated with new visual effects. You don’t even have to know javascript to use it. Bring life to your user interface with a single line of code ! Read more on project home page: http://top.touk.pl/confluence/display/top/GWTaculous

— Previous article

Windows 7 - problem with login to your web application

Next article —

Getting rid of null parameters with a simple spring aspect

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?