Blog

Asciidoctor uses Arquillian and Docker to easily ensure that AsciidoctorJ works into WildFly AS

Language EN / Timereading 10 mn
Overview

This post explains how we execute Arquillian tests for AsciidoctorJ into a Docker container, so we’ll talk about :

It’s been a while since I wrote here but like many technical bloggers (I guess), I’ve a lot of blog posts on draft mode. And I’ve a lot to write about 2014 which was an AMAZING year : indeed, thanks to the Asciidoctor project and Java EE 7 / WildFly technologies, I gave 2 talks at DevNation, San Francisco to speak about Open Source projects :) and I reviewed a book.
But I’ll blogged about this awesome experience soon.

So, what is this post about : Docker ? Asciidoctor ? Arquillian ?

AsciidoctorJ Docker containers managed by Arquillian
Figure 1. The power of Arquillian & Docker for AsciidoctorJ integration tests

You’ve just read the title and you said :

  • "Oh no ! Not another post about Docker!",

and I want to answer

  • "Well, it’s 2015, is it possible to write a blog post without mentioning Docker ?"

To be serious, it’s more a blog post about the AsciidoctorJ project and how Docker helps us to easily check that it’s possible to execute AsciidoctorJ into a Java EE application server like WildFly.
So it’s not a post about Docker itself but more a use case where Docker is the key to the ease of tests…​OK you’re right, it’s about Docker :)

Java EE 7 and WebSocket API for Java (JSR 356) with AngularJS on WildFly

Overview

This blog post describes the Java API for WebSocket Protocol (JSR 356) (which is one of four newest JSRs for the Java EE 7 platform) and provides a concrete application deployed on WildFly 8 and available online on OpenShift.

  • [FR] La version française (HTML ou PDF) de ce post est basée uniquement sur la démonstration avec l’API Javascript sans AngularJS.

Once you will have read this post, you will be able to understand Arun Gupta's definition about what is it possible to do with WebSocket technology.

"WebSocket gives you bidirectionnal, full duplex, communication channel over a single TCP."
-- Arun Gupta (Java EE Evangelist chez Oracle) - Devoxx UK 2013


Java EE 7 et l’API Java pour WebSocket (JSR 356)

Cet article présente et met en oeuvre à travers un exemple concret et disponible en ligne, une des 4 nouvelles JSRs de Java EE 7, à savoir l’API Java pour communiquer via le protocole WebSocket (JSR 356), .

Après la lecture de cet article, vous devriez être en mesure de comprendre la définition de ce qu’il est possible de faire avec le protocole WebSocket, donnée lors de Devoox UK par Arun Gupta :

WebSocket gives you bidirectionnal, full duplex, communication channel over a single TCP.