Skip to main content

JBoss Fuse - Implementing WebService with Camel using CXF SOAP and Restful with CXFRS. Part Two

Continue from last post, this time I am going to add a restful web service endpoint to our insurance application, and show you use the CXF producer. :)

Similar to CXF web service, we need to create a resource file, but this time, instead of an interface, we need to create a java class. Within the resource class file, we have specify 2 things, the context path and the url path of each functions for the restful service. So in the java file below, you will see that I have declare "status" context path for our status service, "/custId/{id}" for getting the status and "/restcancel/{polno}" for canceling claim with restful API.

package org.blogdemo.claimdemo;


public class StatusService {
	public ClaimStatus status(@PathParam("id") String custId){
		return null;

	public ClaimStatus restCancel(@PathParam("claimNo") String claimNo){
		return null;

After creating the resource file, we need to register the restful endpoint in the camel context, it's very similar to the the SOAP one, by setting the address and service class which points to the resource file you create. That's it.

<cxf:rsServer id="statusEndpoint" address="http://localhost:9191/cxf/status" serviceClass="org.blogdemo.insurancedemo.StatusService" />

That's all we have to do to created the restful endpoint. Then adding a method in the processor for status check.

What about the rest cancel function?  Remember we already have a web service that does the cancel operation? Now what happens if we want to reuse it? it's a piece of cake, there are several ways of using the CXF producer,  we can specify to send data into different format, we could do, PAYLOAD, MESSAGE and POJO. You must know how much I love using POJO, so yes, I am going to use POJO for sending the message. The difference between these are simply just different format of data we are sending via this endpoint, with PAYLOAD, you will need to send a SOAP message.

For CXF producer with POJO data format, we need to prepare
1. header operation name
2. body content

The header operation name is the service you want to call and with POJO data format, you will need to put everything into a List. Within the processor, you will see me placing the content into a ArrayList.
	   public ClaimStatus status(String id) throws Exception {
	       // get the id of the input
	   	//ClaimInput input = exchange.getIn().getBody(ClaimInput.class);

	   	System.out.println("ClaimInput :["+ClaimInput.class.getPackage().getName()+"]");
	       // set reply including the id
	   	ClaimStatus status = new ClaimStatus();
	   	return status;
	   public List prepareList(String polno){
		   final List params = new ArrayList();
		   return params;

This is what my camel route looks like. This time, I use content base routing to redirect to my desire processing bean and method.

                ${header.operationName} == "status"
                ${header.operationName} == "restCancel"

Lastly, I will deploy the application onto Fuse Fabric. Don't forget to setup your feature list.
You will see the application route running here.

And the registry can also be found here.

Video demo part Two.

Code Repo :

Hope you enjoy me CXF insurance demo.


Ram Arshad said…
hai christina Lin, i have small doubt regarding the best approach or how to call a DownStream webservice from the actual service using spring.xml
it will be great help if you suggest on this thanks

Actually i have created stub or mock service (using spring.camel.xml) and i am trying to call this service in actual service implementation.i am not able to get the clear idea how to register the downstream(Stub) in the actual service.
Note:i am using xslt init because req coming from upstream is different to downstream request.
after doing all this i am seeing below error in my console

i would like to share the codes also to do that can you provide any mail.
Hi Christina,

Are there any caveats implementing Restlet directly on route (like on instead of Java classes for CXFRS? Do you have some guidance about best practices exposing production REST services with JBoss Fuse?


Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …