Java Weekly 41/15: Java Puzzle, Java Legend ebook, Batchlets
The week’s hottest Java links are here again with Thorben Janssen bringing us an incredibly cool set of Java puzzles, the legend of the Java programming language and the pros and cons of implementing a Batchlet. Stay tuned!
This post originally appeared on Thorben Janssen’s Java EE blog, where Java news is published weekly: thoughts-on-java.org.
There are several different ways to handle expected Exceptions in your JUnit test. Rafal Borowiec gives an overview about them and explains when to use which: Different ways of testing exceptions in Java and JUnit.
Do you like Java puzzles? I personally love them. If it is the same for you, then you should have a look at Alex Zhitnitsky’s post 5 Weird Java Questions That Will Make Your Head Spin.
[…] please don’t use it in real life Java applications! Unless you’re trying to troll someone […]
Be prepared to get really confused by some of the code snippets and please don’t use this in a real project!
Ben Evans wrote a short book about Java, its history and future. You can currently get it for an email signup at O’Reilly: Java: The Legend.
The Java Batch specification allows you to take full control of your batch job by implementing a Batchlet. The downside of it is, that you have to take care of several things yourself, e.g. providing a way to stop it. But no worries, that is not too difficult and Mark Struberg explains it in his recent blog post: Being ‘unstoppable’ – a Batchlets tale.
Java EE 8
The Ozark team released their second milestone of the MVC reference implementation. It corresponds to the EDR2 release of the MVC specification. You can download it here and read the release notes here.
Nigel Deaking posted an updated proposal for the JMS 2.1 specification on the mailing list. One of the main changes is the replacement of the @JMSListener annotation with 3 new ones: @JMSQueueListener, @JMSDurableTopicListener and @JMSNonDurableTopicListener. You can find the updated chapter and more information about the changes in his email: JMS MDB improvements.
This and that
Do you call yourself a senior developer? If yes, what does it mean to you?
Kamil Lelonek wrote an interesting article about what being a senior developer means to him, the four stages of competence and why the title is not easily transferable to another company: What does it mean to be a senior developer?