Coming from a Java background, Scala looks real nice. So does Buildr. So I just had to try them out with Spring and JPA. Here’s a sample CRUD project that exercises basic JPA features with the aforementioned technologies.
First install Buildr as per http://buildr.apache.org/installing.html#jruby, unzip the project archive, cd to project root directory, then run buildr clean test.
You may also find http://buildr.apache.org/languages.html#scala useful.
Tested with JDK 6, JRuby 1.5.1, Buildr 1.4.0 and Scala 2.7.7.
Here’s a sample configuration file for HTTP digest authentication with Spring Security 3.0.x. Have a look at the xml comments for details.
The configuration was produced following the guidance given in Luke Taylor’s recent blog entry.
UPDATE: Apparently this can also be done using the security namespace like so:
<http entry-point-ref="digestAuthenticationEntryPoint">
<intercept-url pattern="/**" access="ROLE_USER" />
<custom-filter ref="digestAuthenticationFilter" position="BASIC_AUTH_FILTER" />
</http>
HTH,
Jukka
After years of “intense” study, I am now officially a master of science. Woohoo! =)
-Jukka
If you’re interested in web app performance testing, have a look at my thesis paper.
- Jukka
Published on
17/07/2009 in
Books.
I recently read 97 Things Every Software Architect Should Know from O’Reilly.
In a nutshell, the book was a short read, concise, and for the most part, readable and useful to the aspiring software architect.
The items provided a good balance between people, business and technology issues. I was able to associate many of the items with real-life experiences. In addition, useful practical principles were presented for each domain.
Unfortunately, there were also a few items that were less useful, mostly due to
- Overly complicated or poorly styled language (making them difficult to read)
- Overuse of fancy metaphors and quotes that did not shed any light into anything as far as I’m concerned
- Lack of real content (though it may be that I simply did not realize their value)
Nevertheless, the book is definitely worth the read.
For the record, I’m not a software architect (yet).
-Jukka