Tag Archive
admin agile ant bea classpath hell coding standards common sense design doh eclipse economics ejb Hibernate humour ide IE intellij ioc Java javaworld junit language design learning management maven meh nytimes opinion patterns personal Politics refactoring Ruby struts suncorp tdd testing testng unit testing usa web app web design weblogic weblogic workshop wotif
Jersey – a review
We’ve been getting more interested in using RESTful web services and AJAX based applications recently. One of the tools we’ve been using with that is Jersey – the JAX-RS (JSR-331) reference implementation. I’ve been using it in anger for about a month now, and thought I’d write up some thoughts I had about it.
The rumours of Ruby’s death are greatly exaggerated…
Sheesh… it seems like every man and his dog is jumping on the latestTIOBE index figures showing a very> small dip in the popularity of Ruby. Talk about lies, damned lies, and statistics…
XML, java.io, and the Composite Pattern
Tony Obermeit posted a question to the AJUG-QLD mailing list asking for help with a problem reading XML snippets. So, I thought I’d help him out, and this is the answer I gave.
*Update*: As pointed out by Pepijn Schmitz, Sun already provided the same solution: java.io.SequenceInputStream
*Another update*: I raised an RFE with Sun for the [...]
Line counts are a silly way to compare languages
Des Traynor did a little post about how languages are not all the same, and Jeff Atwood jumped in with a C# version. Java came out looking really bad at 15 lines for a simple program, but frankly, the reason isn’t because of Java; it’s because of the coding styles used.
Comparing coffee with gemstones
There’s a couple of posts going around about another post comparing Ta-Da with Bla-Bla Look, folks, this isn’t comparing the two languages: this is comparing different coding styles, that strangely enough value different things!
Beware of unlocalised JREs
This is a cautionary tale of US-only JREs and non-US countries, such as The Lucky Country I call home.
Controlling your log4j settings
Nick over at the System Mobile Web Log was having trouble with Log4J and his unit tests. Seems that he was getting the log4j.properties file from XDoclet, instead of the one he wanted.
Don’t you hate it when your expectations crash?
I just discovered that Checkstyle doesn’t (yet) support Java 1.5. I found myself shocked by this for some reason; the Checkstyle project is such an active and evolving one that I just didn’t think they wouldn’t have put in some 1.5 support yet.
/** Still no comment */
Cedric takes exception to my earlier post another who didn’t get what I was saying. I think that says a lot for my ability to explain ideas, uh?
A feature that I would like in Java 1.5 that’s not there…
Looking back over the notes from the Dev Day I took, I was reminded of a feature that I would have liked to have seen in 1.5: named parameters.