In this exercise, I will demonstrate an approach to converting an Axis2-based web service contained within a web application running on JBoss 7, to a JAX-WS-compliant web service running on the JBossWS framework. For JBoss developers, JBossWS is a great choice for a web services runtime as it is based on the popular, and mature, Apache CXF framework. The Eclipse (Juno) IDE configured with the JBoss Tools 4.0 plugin will be the primary tools used in this effort.
The goal of this post is to provide a high-level discussion of JBoss OSGi and to increase awareness of its potential benefits and drawbacks to a Java enterprise architect/developer.
The goal of this post is to discuss at a high level the radical change in the class-loading mechanism used by JBoss, and some of the benefits of this change. Since the inception of JBoss, issues around how Java classes are discovered and loaded into the server have never been fully addressed. For those of us who have faced an unexpected ‘ClassCastException;’ troubleshooting those issues has often been a mystifying experience. Especially since the class-loading strategy has changed over multiple releases of JBoss through the years. Additionally, most developers do not wish to spend their time investigating how their classes are loaded and isolated from other applications running on the server. Our focus is on getting the business logic right, in compliance with the Java EE spec.
Red Hat and the JBoss Community recently announced that they will be releasing a single compiled binary under the EAP.Alpha terminology, rather than posting a community release on the community site and a separate EAP early release on the Red Hat site. This naming change has confused some members of the community, but rest assured the EAP.Alpha release is still under the LGPL as per previous JBoss Community releases.
“Federation” is a term that has been floating around the modern parlance of enterprise architecture and integration for a long while, but with the flood of interest in cloud computing, it is back in the spotlight. For many organizations, choosing a federation platform with open standards is important, and for many of those same organizations, the open source platform is preferable. This article walks IT decision makers through the technical landscape, and gives a fundamental overview of the marketplace of solutions available today.
This final post in my blog series explains how to set up a data source in JBoss, and how to secure the password in the data source using PicketBox Vault. As previously, this article uses a tagged release of JBoss that does not have a binary release available. The tagged release is JBoss 7.1.3.Final. The latest binary release of JBoss available for download is JBoss 7.1.1.Final.
If you read a post on The Enterprise OSS Blog, please leave a comment. Let us know what you think, even if it's just a few words. Comments do not require approval, but they are moderated.OpenLogic reserves the right to remove any comments it deems inappropriate.