Category: Uncategorized


Few days ago, Oracle released pre-configured Oracle SOA/BPM Suite 11g PS5 ( VirtualBox image that is available for testing and evaluation purposes.

The VirtualBox image contains the following software:

  • Oracle Enterprise Linux (64-bit) EL 5 Update 5
  • Oracle XE Database 11.2.0
  • Oracle SOA Suite (includes Service Bus)
  • Oracle BPM Suite
  • Oracle Webcenter Content (Enterprise Content Management)
  • Oracle Webcenter Suite
  • Oracle JDeveloper
  • JRockit R28.2.0-79-146777-1.6.0_29s
  • Sun Java SDK 1.6.0_29-b11

It is available for download on this link.

No tags Hide

Recently, while I was trying to fit standard fault handling mechanisms to all of the invoke activities within a business process, using IBM WebSphere Integration Developer and Process Server 7.0, I have come across a very unpleasant problem:

CWWBF0135E: Starting the business process application ‘PRIO_SklepanjePoD_1.0.0App’ failed due to pending business process template updates. (more…)

No tags Hide

IBM Champion Award

Matjaz B. Juric has been selected as an IBM Champion for WebSphere software.

Excerpt from the original letter: “IBM Champion program recognizes individuals who make outstanding contributions to our IBM communities by evangelizing and advocating solutions; sharing their knowledge and expertise; and helping nurture and grow independent communities.

After reviewing your nomination and related information from communities with which you are involved, the selection committee agreed that your efforts over the last 12 months distinguish you as a true IBM Champion. You are among an elite group of enthusiasts to be chosen for this recognition. Congratulations!”

This is the third award for Matjaz B. Juric, who has also received Java Champion and Oracle ACE Director awards.


No tags Hide

Lately, when I have been trying to install a new version ( of IBM BPM environment, I have encountered an unexpected problem. I have installed Integration Designer along with Process Server and BPM Process Center (PC) on the same virtual machine. After installation, I have first created a Process Server Profile and after and then a PC profile.
Creation of both profiles went smoothly and both profiles started normally. Then, I opened Process Center Console on the second profile and downloaded Process Designer (PD) installation files. I installed PD and tried to open it. And there was a surprise. Although I have just downloaded files from process center, which was therefore obviously running, PD has displayed the following error: “Attempt to connect to the Process Center failed. Verify that the server is running.”. (more…)

, , , , , , , , , Hide

Slovenian Innovation Forum has been kicked-off

This article serves as a tutorial on how to develop Web Service using Axis2 and JAXB XML data binding.

Current version of Axis2 framework at the time of writing this tutorial is 1.6.1. Its integration in Eclipse java development tool supports two types of wizards for creating web services: Web Service Wizard and Web Service Client Wizard. Using these two wizards enables us to build client-side and server-side web service artefacts for Axis2. Its preferences include selecting XML data binding type. Supported types in these wizards are ADB and XMLBEANS. Although when using supplied Web Service wizards there are only those two supported data bindings in fact Axis2 also supports JiBX and JAXB data bindings.

Because the standard development of Web Services compliant to JAX-WS 2.1 is using JAXB 2.0 data binding we will show how to develop web services under these technologies. For this we will not use supported wizards, but WSDL2Java command line tool. This tool is supplied in downloaded Axis2 package. Be aware that WAR (Web Archive) Axis2 distribution does not include mentioned tool.

For this tutorial we will develop a Top Down Web Service from supported WSDL.

We will assume that we already have installed Tomcat server version 7.

Preparing Eclipse environment.

To prepare Eclipse environment for implementing our web service we must set Axis2 runtime location. In Eclipse we enter “Preferences” (Window -> Preferences), than we navigate to “Web Services” -> “Axis2 Preferences”, where we set “Axis Runtime Location” to the location of extracted Axis2 folder (Image below). After this we can also prepare User Libraries under “Java” -> “Build Path” -> “User Libraries” where we first add new Library, and then we add all JAR files from “lib” directory under extracted Axis2 directory to this library.

After this we must add AXIS2_HOME environment variable (assuming we already have JAVA_HOME environment variable set) which points to installation directory of Axis2 e.g. “C:\axis2-1.6.1”.

Preparing project for developing Web Service.

We will develop our sample Web Service into Dynamic Web Project. For creating project with support for Axis2 we must select proper facets. We can do this when creating new “Dynamic Web Project” using button “Modify” (Image below).

We must select “Axis2 Web Services”. Since current version of Axis2 runs on Servlet version 2.5 or less it is also necessary to change “Dynamic Web Module” version to 2.5. Note that this is not necessary if we are using target runtime that does not support Web Module higher than 2.5.

At this stage we have prepared our project for building a web service.

Preparing WSDL Web Service description.

For the purpose of this tutorial creating WSDL description does not hold high priority. That is why we will skip the part of creating one and will use one supported on this link: WeatherServiceWSDL

Generating Java skeleton.

As mentioned earlier in this tutorial we will Casino Online use WSDL2Java command line tool (we can find it in axis2 installation directory under directory “bin”). For generating Java Skeleton classes we will use the following command shown on image below:

wsdl2java.bat –o C:\EclipseWorkspaces\DefaultWorkspace\WeatherService -ss -d jaxbri -uri C:\WeatherService.wsdl

Attributes explanation:

  • o – Path where Java skeleton will be generated (usually web project path).
  • ss – Marks generating server side artefacts
  • d – Selected data binding for generating Java skeleton, “jaxbri” marks JAXB Reference Implementation data binding.
  • uri – supported is local disk path or URL of WSDL file.


After generation Java skeleton we must implement web service. Image below shows generated classes.

Implementation classes are named “*”. There we implement generated method that represents our Web Service operation. Note that sometimes it is necessary to refresh file list in Eclipse Project Explorer for generated files to be visible.

Packaging Web Service.

When generating web service Java Skeleton, WSDL2Java tool also creates ant build file for building and packaging generated web service. This file is “build.xml”. Our next task is to run this Ant task. For the purpose of this tutorial we will add a builder that uses generated Ant task to prepare our web service for deployment. Another option would be manually running this task with Ant.
This we will do by Right Clicking on project that holds generated classes and selecting “properties”. Under “builders” we add new Ant builder. Only thing we must do when configuring this builder is to select build file. We must select generated “build.xml” file as seen on image below. Recommended is also to change builder name.

After setting new builder we see build log on console. Building must be successful.

Deploying Web Service.

Result of successful building is Axis Archive package, which includes build web service. Procedure in previous stage creates this kind of package under “build/lib” folder in our project. Archive name in the case of this tutorial is “WeatherService.aar” and it includes developed services class files. We have different possibilities on how to deploy Web Service packed this way. We can deploy it under Axis administrative console, or we can manually add it to Axis service repository. For the purpose of this tutorial we will manually deploy it on Axis runtime which has been already added into our project at stage 2. We must do two things. First one is copying Axis archive file, in our case is “WeatherService.aar” to “WebContent/WEB-INF/services” folder that represents Axis2 repository. Next step is to add “WeatherService.aar” into “services.list” text file situated in the “services” folder.

Files used at this stage of the tutorial are shown in image below.

Running Web Service.

After completed all this steps successfully, we are now able to test developed Web Service. WSDL should be accessible, when using default configuration, at address like: http://localhost:8080/WeatherService/services/WeatherService?wsdl

Source Project

You can download a Eclipse snapshot of this project from this link: WeatherService

, , , Hide

Presentation at OpenBlend

Today, we had a presentation on SOA Architectural Patterns on the OpenBlend conference, which took place where to buy levitra cheap at Ljubljana Castle. There were a lot of participants. An amazing event, very recommended!