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 Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.



JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…