DevOps JSR aka Java Config JSR

On twitter there were some rumbles on a Java Config aka Devops JSR. I went to read it’s mailinglist and it gave me a bit the creeps! And I thought  “ah no 140 chars is to short for a decent rant! so I wrote a rant on RebelLabs

Get going, what are you still reading here? You should be reading the link.

HTTP Statusses 7XX

Now add even more fun with randomizing HTTP Status 7XX.

A new version for Jersey has been released.

With using getRandom method you can return a randomized HTTP 7XX status (e.g. instead of sever error 500 or on unimplemented API calls )

Get the dependency with

<dependency>
    <groupId>be.redlab.jersey</groupId>
    <artifactId>http-7xx</artifactId>
    <version>1.1</version>
</dependency>

Release Info and tag at github

The new release also removes the rebel.xml file from the resources. Although it’s not in the source control, it was in the released artifact due to building that locally. The release is a bit over time due to my gpg key that was expired, that’s fixed now.

/**
 * Puzzle your users with returning a pseudo random HttpStatus7xx on every call.
 *
 * @return a pseudo randomly chosen HttpStatus7xx
 */
public static HttpStatus7xx getRandom() {
	return HttpStatus7xx.values()[RND.nextInt(MAX_RND)];
}

Results of ‘a small survey about logging’

I’ve recently conducted a survey about logging. Whilst it’s not a complete correct survey ( I left out Log4j2 oops! Sorry, next time better! And I will definitely try it out )

You can now follow up on the results here on RebelLabs , they gave me the opportunity to post the results there. And so I did. Head over to RebelLabs and read the summary!

uselogging