Few JBoss / WildFly administrators are aware that the application server has a management interface based on HTTP/JSON based API. This can be an easy shortcut if you want to collect quickly information from your servers with as little as a browser bookmark.
Managing JBoss - WildFly using HTTP/JSON API
Java EE Batchlets with WildFly tutorial
This is the second tutorial about Java API for Batch Applications (JSR-352) on WildFly application server. In the first Java EE Batch Tutorial we have learnt how to use chunk steps which are iterative executions of read/process/write operations on a set of items. Batchlets, on the other hand, include activities which are not executed in an iterative style as chunk but as atomic activities. In short a batchlet is a step which is called once. It either succeeds or fails. If it fails it can be restarted and it runs again.
Using Log4J with JBoss AS 7 and WildFly
Using log4j with JBoss AS 7 has had a troubled history and I'd like to offer a comprehensive guide with this article so that you can save a few headaches. Let's start with the newest version of the application server and later we will see how to use log4j with jBoss AS 7.
Read WildFly 8 log files using the CLI
In this short tutorial we will learn how to inspect the WildFly 8 log files from the Command Line Interface.
Using try-with-resources to close database connections
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.
jBPM 6 Web application example
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.
Page 4 of 48