We’ve just published code review application built during this year internship @touk. It starts to look as a usable product, though it’s not ready yet and you can still change its shape. Check the freshest deployment and leave your feedback. If you want to get involved as a developer fork us on github!
— Previous article
Rails Girls Warsaw
Next article —
<!--:pl-->TouK na WGK 2012<!--:--><!--:en-->TouK on WGK 2012<!--:-->
You May Also Like
Visualizing GIS data in JavaFX 2.0 beta using GeoTools
- byRafal Rusin
- June 13, 2011
Geographic data mostly comprises of polygon coordinates sets along with attributes, like country or city name, etc. This is quite easy to visualize in JavaFX, which supports rendering for SVG paths. In the article, I show how to read such GIS data from...Geographic data mostly comprises of polygon coordinates sets along with attributes, like country or city name, etc. This is quite easy to visualize in JavaFX, which supports rendering for SVG paths. In the article, I show how to read such GIS data from...
Grails with Spock unit test + IntelliJ IDEA = No thread-bound request found
- byRafał Nowak
- September 17, 2013
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?
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?
Oracle ODBC dla Windows
- byBartek Zdanowski
- January 11, 2011
Potrzebowałem dostępu do bazy Oracle przez ODBC. Niestety Oracle’owy driver odbc jest inny niż wszystkie :-), bo nie…