tag:blogger.com,1999:blog-51590559660942714702024-11-01T08:39:03.283+01:00Architecture exist in the details as well.Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-5159055966094271470.post-51398375246941053972013-08-28T11:50:00.000+02:002013-08-28T11:50:30.785+02:00

Spock framework is a very intuitive specification test framework, and I cannot really say how much I appreciate it.... The flavour of writing it in near-english and with a tabular dataset (and a good Mock framework too) makes it extremely easy to understand for any layman.. Given that you add the plugin in your grails-app/conf/BuildConfig plugins { test ":spock:0.7" } And modify

Anonymoushttp://www.blogger.com/profile/06186321190571609088noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-9648708270716802792013-08-23T13:32:00.001+02:002013-08-23T13:37:18.943+02:00

One of the fantastic things about Grails is the spring integration and spring injection. Even plugins can inject beans of different flavour into a spring context and modify everything accordingly. Accessing any bean is a bliss with the dependency injection, which mostly is by name, but what do you do if you can't remember the name of bean to inject. 1 Injecting by type If you like me think

Anonymoushttp://www.blogger.com/profile/06186321190571609088noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-17168891995750074592013-07-29T14:49:00.001+02:002013-07-29T14:49:33.292+02:00

Google Guava is one of the greatest utility libraries to have around. It solves a lot of problems that using a simple map simply just don't do, such as expiry and size considerations and especially multi-threading. Consider this pattern: def cache = [:] def get(key) { element = cache[key] if (!element) { element = loadElement(key) cache[key] = element } return element } It

Anonymoushttp://www.blogger.com/profile/06186321190571609088noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-63550005424440662172011-10-05T20:31:00.004+02:002013-07-25T16:12:55.949+02:00

I have been thinking real hard lately what would the the top things I would look for in a build environment. Granted I have had amble experience from early days and until now, which include very prehistoric makefiles and shell scripts up til the more modern equivalents. This includes ant, ant-ivy, maven-1, maven-2, as well as gradle and rake, and quite recently buildr. I see a lot of people

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-68108621612075271962008-06-13T12:24:00.006+02:002013-07-25T15:56:16.038+02:00

A while ago, when reading about a JavaScript template engine, I encountered a language construct called forelse The construct was placed to accomodate for the case where there was zero iterations in a for loop. This is quite handy in web scenarios, for instance when you need to present a list, and the list is empty. You would then do something like this: for (SearchItem item : items) { ... (

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-75307664580121838632008-05-26T12:31:00.004+02:002013-07-25T16:53:58.861+02:00

I coincidentially came across code similar to the section below: private boolean connected = false; ... synchronized (connected) { if (!connected) return; // If connected, change to disconnected and proceed, otherwise do nothing connected = false; } Which gives rise to 3 vital things to know about synchronization: 1) Synchronize on the object

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-29313137073445728662008-03-21T10:38:00.002+01:002008-03-21T10:55:52.380+01:00

For some reason you always end up with a NPE when you least of all need it.The problem with NPE is usually that you can see WHEN you use the object that somebody has provided the WRONG information earlier on. NPE always means trying to trace backwards in the code, and find suspects, and that is not always possible.Imagine a simple attribute on a class (say name). You will see NPE when it is USED,

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-62680951981795474752007-11-11T14:08:00.000+01:002007-11-11T16:33:39.263+01:00

I remember a tutorial once, which explained how to install rails like this:gem install rails -y --no-rdoc --no-ri --include-dependencies.How, come the user, as a novice, does not need the documentation?Well, the explanation was simple. If you include the documentation, it will take a long time to complete the installation.Why do they think, that the new user, which is struggling to learn a topic,

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-40375005177433691262007-11-11T13:45:00.000+01:002007-11-11T14:08:31.985+01:00

I was just reading Ola Bini's new book, Practical JRuby on Rails, when I stumbled upon this paragraph:... As such, testing should always be written concurrently while writing the implementation code. Alas, due to space constraints, this book won't contain much testing information.This is definitely not the first time, I encounter this. Quite contrary I believe most of the books I read in which

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-26032046956934322262007-11-05T11:51:00.000+01:002013-07-25T16:57:05.843+02:00

Well, the title says it all, doesn't it. One thing I have come across continously over the years is the lack of thought developers have about collections. I actually managed to find it again last week in the JRuby source, but it could basically have come from anywhere. Take a look at this simple method, which I will use as an example: class RubyModule { public Map getMethods() { return

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com1tag:blogger.com,1999:blog-5159055966094271470.post-65701189281166264062007-10-23T11:25:00.001+02:002007-10-23T11:25:22.053+02:00

I recently got tired of my previous blog because of the endless attacks and spoofings, and I decided to stop using more time on it and just use this blog instead.I still have all the previous posts somewhere, but it is unlikely that they ever will be posted here. It just takes too much time. Anyway, most of it is probably outdated anyway.Powered by ScribeFire.

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-35689523792839356892007-10-15T13:50:00.000+02:002007-11-11T13:43:32.546+01:00

I usually do a lot of introductionary java courses, and have to learn people everything from scratch over and over again. The course material I use has remained stable for many years, until the launch of java 5, when the language really started to move away from its core. It is clearly a response to pressure from other languages breathing down its neck such as C#, Ruby, Groovy and others.

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-11671587872438500202007-10-05T13:55:00.000+02:002007-11-11T13:43:05.131+01:00

There are times when you need access to a constructor for one specific purpose, but the constructor is not and should not be public. To me these times are usually around unit testing when I want to manipulate my data structures into a testable state. Let me show you an example: I have an object which reads its configuration from the classpath and now I want to test it. To do this I would

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0tag:blogger.com,1999:blog-5159055966094271470.post-91837679325222051542007-02-21T09:46:00.000+01:002007-02-21T09:48:00.407+01:00

Hi there,Eventually we all turn to google, and so I've opened a blog account as well here.Otherwise I use the http://www.javaekspert.dk for my stuff.

Niels Bech Nielsenhttp://www.blogger.com/profile/00036467164500469290noreply@blogger.com0