<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;A08CQX8_eCp7ImA9WhRRFE4.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470</id><updated>2011-11-28T00:24:20.140Z</updated><category term="best practise" /><category term="jruby" /><category term="enhancement" /><category term="java" /><category term="work" /><category term="oo" /><category term="development" /><category term="threading" /><title>Javaekspert - Code Architects</title><subtitle type="html">Architecture exist in the details as well.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://javaekspert.blogspot.com/" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>15</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Javaekspert" /><feedburner:info uri="javaekspert" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;A04BRHo-eCp7ImA9WhdUGE4.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-6355000542444066217</id><published>2011-10-05T19:31:00.004+01:00</published><updated>2011-10-05T19:39:15.450+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-10-05T19:39:15.450+01:00</app:edited><title>5 Little Things I Want from a Build System</title><summary>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 arguing</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/6355000542444066217/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2011/10/5-little-things-i-want-from-build.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6355000542444066217?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6355000542444066217?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/-uZA17ZiSI0/5-little-things-i-want-from-build.html" title="5 Little Things I Want from a Build System" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2011/10/5-little-things-i-want-from-build.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEEFSXk_cSp7ImA9WxFXEUQ.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-4916336422675042410</id><published>2010-05-18T15:23:00.001+01:00</published><updated>2010-05-18T15:23:38.749+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-18T15:23:38.749+01:00</app:edited><title>A word from the Trenches</title><summary>I’m tired of building the same software anytime. Does anybody know of a good data distribution mechanism for tabular data..?  </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/4916336422675042410/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2010/05/word-from-trenches.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/4916336422675042410?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/4916336422675042410?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/ZqZEIEhwVjY/word-from-trenches.html" title="A word from the Trenches" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2010/05/word-from-trenches.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUQGQH8zfip7ImA9WxRbFkg.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-6810862161207527196</id><published>2008-06-13T11:24:00.006+01:00</published><updated>2008-12-07T13:42:01.186Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-07T13:42:01.186Z</app:edited><title>One missing language construct</title><summary>A while ago, when reading about a JavaScript template engine, I encountered a language construct calledforelseThe 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) {  ... (do </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/6810862161207527196/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2008/06/one-missing-language-construct.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6810862161207527196?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6810862161207527196?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/mWJEyi1RaBA/one-missing-language-construct.html" title="One missing language construct" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2008/06/one-missing-language-construct.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YDR3Y5eip7ImA9WxdSF0Q.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-7530766458012183863</id><published>2008-05-26T11:31:00.004+01:00</published><updated>2008-05-26T11:52:56.822+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-05-26T11:52:56.822+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="best practise" /><category scheme="http://www.blogger.com/atom/ns#" term="threading" /><title>3 Vital Things to Know about Synchronized</title><summary>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, not the </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/7530766458012183863/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2008/05/3-vital-things-to-know-about.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/7530766458012183863?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/7530766458012183863?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/Y64brUZA-PM/3-vital-things-to-know-about.html" title="3 Vital Things to Know about Synchronized" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2008/05/3-vital-things-to-know-about.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUQBQ30zeCp7ImA9WxZVEEQ.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-2931313707344572866</id><published>2008-03-21T09:38:00.002Z</published><updated>2008-03-21T09:55:52.380Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-03-21T09:55:52.380Z</app:edited><title>Tracking the NPE</title><summary>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,</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/2931313707344572866/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2008/03/tracking-npe.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2931313707344572866?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2931313707344572866?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/XlPt-nLeKKo/tracking-npe.html" title="Tracking the NPE" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2008/03/tracking-npe.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMFSHsyeCp7ImA9WB9VEUs.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-9203561694440684638</id><published>2007-11-27T12:26:00.001Z</published><updated>2007-11-27T12:26:59.590Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-27T12:26:59.590Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="jruby" /><category scheme="http://www.blogger.com/atom/ns#" term="threading" /><title>Jruby is heavily developing</title><summary>I have tried to help out with the JRuby project, after Charles Nutter requested help with the 1.1 release, but it really disappointed me at first.I remember going straight into Jira, and examining the current blockers and criticals to pick a few problems. The two problems I immediately picked were both concerned with race conditions, and I managed to work quite a while to drill down to the actual</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/9203561694440684638/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/jruby-is-heavily-developing.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/9203561694440684638?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/9203561694440684638?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/p_COljVR2ao/jruby-is-heavily-developing.html" title="Jruby is heavily developing" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/jruby-is-heavily-developing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UFSHw9eyp7ImA9WB9XF0Q.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-6268095198179547475</id><published>2007-11-11T13:08:00.000Z</published><updated>2007-11-11T15:33:39.263Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-11T15:33:39.263Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="development" /><title>Who needs documentation anyway?</title><summary>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,</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/6268095198179547475/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/who-needs-documentation-anyway.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6268095198179547475?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6268095198179547475?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/A77xBE-MalA/who-needs-documentation-anyway.html" title="Who needs documentation anyway?" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/who-needs-documentation-anyway.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEIFQHczfSp7ImA9WB9XF0U.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-4037500517743369126</id><published>2007-11-11T12:45:00.000Z</published><updated>2007-11-11T13:08:31.985Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-11T13:08:31.985Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="development" /><category scheme="http://www.blogger.com/atom/ns#" term="best practise" /><title>Best Pracise obstructed by Bad Instructors</title><summary>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 </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/4037500517743369126/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/best-pracise-obstructed-by-bad.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/4037500517743369126?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/4037500517743369126?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/FGbT8RCfWlw/best-pracise-obstructed-by-bad.html" title="Best Pracise obstructed by Bad Instructors" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/best-pracise-obstructed-by-bad.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8NRX8-fCp7ImA9WB9XEks.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-2603204695693432226</id><published>2007-11-05T10:51:00.000Z</published><updated>2007-11-05T12:48:14.154Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-05T12:48:14.154Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="jruby" /><category scheme="http://www.blogger.com/atom/ns#" term="oo" /><category scheme="http://www.blogger.com/atom/ns#" term="threading" /><title>overexposing java collections is bad practise in multi-threaded environment</title><summary>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 this.methods;</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/2603204695693432226/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/overexposing-java-collections-is-bad.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2603204695693432226?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2603204695693432226?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/g6rC8I67tHk/overexposing-java-collections-is-bad.html" title="overexposing java collections is bad practise in multi-threaded environment" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/overexposing-java-collections-is-bad.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UAQX06eSp7ImA9WB9XFUs.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-2993100040831479070</id><published>2007-10-28T11:19:00.001Z</published><updated>2007-11-08T22:34:00.311Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-08T22:34:00.311Z</app:edited><title>Got myself  a helicopter</title><summary>I took the kids to Toys'R'us yesterday to find a present. For some reason we all left with something.My son got some more Thomas the Engine tracks, my daughter got a Tamagutchi, but I...Just couldn't help myself and bought a helicopter. Lightweight and fun, but no API....</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/2993100040831479070/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/10/got-myself-new-toy.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2993100040831479070?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/2993100040831479070?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/B4M1-G36lMc/got-myself-new-toy.html" title="Got myself  a helicopter" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://bp1.blogger.com/_OsaWapHBkl0/RyRwc2bM7jI/AAAAAAAAAAM/tLSIjB1NXIM/s72-c/DSC00561.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/10/got-myself-new-toy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cCQHgyeCp7ImA9WB9QE00.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-480013999167804583</id><published>2007-10-24T22:29:00.000+01:00</published><updated>2007-10-25T10:37:41.690+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-10-25T10:37:41.690+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="jruby" /><category scheme="http://www.blogger.com/atom/ns#" term="work" /><title>Helping out in JRuby land</title><summary>Headius posted a request for help in his blog lately.As usual I just dig into it.So for now, I'll put my pet thought project on the shelves, and pretend to do some real work :-)</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/480013999167804583/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/10/helping-out-in-jruby-land.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/480013999167804583?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/480013999167804583?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/qRh0Vfc-h3c/helping-out-in-jruby-land.html" title="Helping out in JRuby land" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/10/helping-out-in-jruby-land.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IGQ34-eyp7ImA9WB9QEU4.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-6570118928116626406</id><published>2007-10-23T10:25:00.001+01:00</published><updated>2007-10-23T10:25:22.053+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-10-23T10:25:22.053+01:00</app:edited><title>Moving in</title><summary>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.</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/6570118928116626406/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/10/moving-in_23.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6570118928116626406?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/6570118928116626406?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/kJYLdzVmXOU/moving-in_23.html" title="Moving in" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/10/moving-in_23.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cFQ3s_fip7ImA9WB9XF0U.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-3568952379283935689</id><published>2007-10-15T12:50:00.000+01:00</published><updated>2007-11-11T12:43:32.546Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-11T12:43:32.546Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><category scheme="http://www.blogger.com/atom/ns#" term="enhancement" /><title>10 reasons why Java is drifting away</title><summary>     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. </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/3568952379283935689/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/10-reasons-why-java-is-drifting-away.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/3568952379283935689?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/3568952379283935689?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/oXiv_e54ubk/10-reasons-why-java-is-drifting-away.html" title="10 reasons why Java is drifting away" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/10-reasons-why-java-is-drifting-away.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4MRH84eSp7ImA9WB9XF0U.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-1167158787243850020</id><published>2007-10-05T12:55:00.000+01:00</published><updated>2007-11-11T12:43:05.131Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-11-11T12:43:05.131Z</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="java" /><title>Semi private constructors</title><summary>     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 </summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/1167158787243850020/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/11/semi-private-constructors.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/1167158787243850020?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/1167158787243850020?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/O_LVknPWjF8/semi-private-constructors.html" title="Semi private constructors" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/11/semi-private-constructors.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEMQXo7fyp7ImA9WBFREEk.&quot;"><id>tag:blogger.com,1999:blog-5159055966094271470.post-9183767932522205154</id><published>2007-02-21T08:46:00.000Z</published><updated>2007-02-21T08:48:00.407Z</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2007-02-21T08:48:00.407Z</app:edited><title>Introducing myself</title><summary>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.</summary><link rel="replies" type="application/atom+xml" href="http://javaekspert.blogspot.com/feeds/9183767932522205154/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://javaekspert.blogspot.com/2007/02/introducing-myself.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/9183767932522205154?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/5159055966094271470/posts/default/9183767932522205154?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Javaekspert/~3/PolMfJbMpXE/introducing-myself.html" title="Introducing myself" /><author><name>Niels Bech Nielsen</name><uri>http://www.blogger.com/profile/00036467164500469290</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://javaekspert.blogspot.com/2007/02/introducing-myself.html</feedburner:origLink></entry></feed>

