Post Profile






CodeSOD: Every Possible Case

From reader Frank comes this delightful Java-flavored head-scratcher: This is from the main request-handling method for a webservice. Counting all of its interesting features is left as an exercise for the reader, but the request data is never modified and the error handling in both catch blocks is the same.... The kicker is that doCalculation() has all its logic inside try {} catch (Exception ex) anyway.
read more

share

Related Posts


ASP.NET Webservices in Java via kSOAP

Programming / Windows Development : CodeProject

Handy bridge between ASP.NET webservices and Java

Java 8 – Default Methods in Interfaces

Technology / Programming : TheServerSide.com

In this article we will explore the Java 8 default method’s feature in interfaces. The Java 8 says “Default methods enable new functionality to be added to the interfaces in libraries and ensure binary compatibility with code writte...

Why even use Java 8 Optional? A crucial point you might be missing

Technology / Programming : TheServerSide.com

Java 8 introduced a type Optional, which can be used to handle potentially missing values. It does so by wrapping a reference (which might be null) and providing some nice methods to interact with the value in case it’s present. To ...

CodeSOD: Split Second Load Balancing

Technology / Programming : The Daily WTF

In case you're not familiar with the concept of a load balancer, the purpose of having one is to spread requests across multiple, identical servers associated with it so as to give the requester the best possible experience. As an a...

Java 8 and the curious case of the non-capturing lambda

Technology / Programming : TheServerSide.com

Roughly a month ago, I summarised Brian Goetz’ peek under the hood of lambda expressions in Java 8. Currently I’m researching for a post about default methods and to my mild surprise came back to how Java handles lambda expressions....

Comments


Copyright © 2016 Regator, LLC