JBoss application server tutorials

This tutorial shows how to use a Java SE 7 feature called try-with-resources to handle Connection, Statement and ResultSet objects which are retrieved from a JBoss / WildFly Datasource.
Prior to Java SE 7, developers needed a finally block to ensure that a resource is closed regardless of whether the try statement successfully completed or not. This required quite a long piece of code to handle safe closing of every objects, especially in the case of a database connection object. 

In this tutorial I'll describe how I have set up my first jBPM 6 application using Eclipse and the jBPM 6 plugin installed on it. The prerequisite to it is that you have correctly installed jBPM 6 using the jbpm-installer. I have described the steps in this tutorial which shows how to shorten the full installation procedure. 

This tutorial is an introduction to the jBPM 6 platform which has now reached its final release, bringing lots of power to your business processes.
For those which are new to jBPM, you should be aware that jBPM is a Business Process Engine that allows defining executing an monitoring your business processes. jBPM is distributed as a set of libraries therefore you are free to choose whether to use it embedded in your applications or simply using it as a BPM Service, for example via the REST API.

In this tutorial we will demonstrate how to retrieve Transaction information from your Java EE applications running on JBoss/WildFly and how to combine this information with the Narayana Transaction Analyser application. 

Before Java EE 7, EJBs were the only component that supported declarative transactions. This made your CDI beans a popular option when used as a glue between the JSF side and the EJB side, which was in charge to complete the transactions declaratively. So, in other words you could choose to either bloat your CDI Beans with Transactional bolierplate code, or add a component (the EJB) which should be in charge to complete the transactions. 

Today the 1.0.0.Final-SNAPSHOT Bill of Material for WildFly 8 and Java EE 7 has been released so we will see how to update our Project Object Module (pom.xml) in order to compile and deploy your Java EE 7 projects on WildFly 8 using Maven.