SOA-Blog.net

Java SQL PreparedStatements can become hard to maintain, especially if you have a lot of parameters in one statement. There is a Helper Class out there called NamedParameterStatement, that was initially written by Adam Crume. It lets you set Parameter using names instead of indexes. I will provide an example to discuss this pattern along with a few code changes using Java Generics.

Building J2EE modules for Websphere with Maven can cause tricky problems. One of those is a org.omg.CORBA.OBJECT_NOT_EXIST Exception after deployment.

Building J2EE Projects for WebSphere with Maven2 is somehow challenging. This is caused by a shallow documentation that is not very detailed on IBM WebSphere issues. I recently encountered a problem concerning the EJB-Client generation, that I want to discuss here.

The WSLA-Plugin helps you to manage your enterprise service level agreements for web services in a simple, structured and easy-to-use model, that is entirely based on IBM's WSLA language specification.

This section will explain how to submit bugs and feature for the Web Service Level Agreement (WSLA) Plugin for Eclipse.

This section provides a quick introduction to service level agreements (SLAs) for webservices, depicts the concept behind the plugin and outlines how you can benefit from it.

This section will contain generated reports derived from Service level agreements based on WSLA data.

This section provides insight into the plugin component architecture, built-in capabilities and technical requirements of the Web Service Level Agreement (WSLA) plugin for the Eclipse platform.

Basically, there are two ways to install the WSLA Plugin for Eclipse:

1. Install the plugin using the WSLA update site.
2. Download a ZIP archive that contains the plugin.

Make sure, that you have read the prerequisites before installing the plugin.