Page History

Overview of the ServiceMix 2.x RSS Binding Example

The following procedure describes how to run the RSS Binding example in ServiceMix and provides details regarding what the RSS Binding does. For information on the business use case, please refer to: Use Case for HTTP RSS Binding.

The HTTP RSS Binding example illustrates:

• use of declarative programming
• how to perform an HTTP RSS binding in ServiceMix

The source code for the HTTP RSS Binding example is located in the ServiceMix installation directory under the examples\httprss-binding directory in the servicemix.xml file. It is recommended that you refer to the source code while reading this document.

This example shows how to use an HTTP binding to handle a simple HTTP post. One component acts as the HTTP server, which listens on http://localhost:8912^{Image Removed}, while another component invokes a remote service, implemented as an URLEndpoint. A simple HTTP client is provided so that a simple post can be sent to the server.

Running the HTTP Binding Example

monitor RSS feeds for changes. The main component of this example periodically polls a list of RSS news feeds and when an update is found the new RSS items are displayed on the console.

Running the RSS Binding Example

1. From a command shell, go to the HTTP RSS Binding example directory:

   Code Block
   cd [servicemix_install_dir]\examples\httprss-binding

   where servicemix_install_dir is the directory in which ServiceMix was installed originally.
2. Then type:

   Code Block
   [servicemix_install_dir]\bin\servicemix servicemix.xml

   To start sending and receiving messages from the HTTP server, send an initial message. To do this, compile and then run a simple HTTP client. The HTTP client used in this example, is built and run from source code using Ant. Execute Ant from the HTTP Binding directory: servicemix_install_dir\examples\http-binding. To run the HTTP client type:
   

   Code Block
   ant

   Ant will compile and run the simple HTTP client, HttpClient, which performs a simple post on the HTTP Server into the ServiceMix container, before returning the results to the console.
   

   Tip
   title Handy Hint
   Add $SERVICEMIX_HOME/bin directory to $PATH variable to simplify execution of the examples.

   
   

Stopping the

...

RSS Binding Example

To terminate the HTTP RSS Binding example, type "CTRL-C" in the command shell in which it is running and answer "y" to the "Terminate batch job (y/n)?" question.

How it Works

The diagram below illustrates the flow of messages through the HTTP RSS Binding components:

Messages flow through the components as follows:

1. HttpClient, a Java stand-alone program, connects to http://localhost:8912^{Image Removed} through the URLConnection class. HttpClient sends the file request.xml to this port.
2. httpReceiver, an HTTP server, being a listener on http://localhost:8912^{Image Removed} receives the message.
3. httpReceiver sends the message to stockQuote as specified in its destinationService property, via NMR.
4. stockQuote sends the message into another service, soapEndpoint for processing.
5. soapEndpoint sends the response to stockQuote.
6. stockQuote sends the response to httpReceiver via NMR.
7. httpReceiver sends the response to http://localhost:8912^{Image Removed}.
8. HttpClient reads the response.
9. The response is printed on the console.

Typical output looks like the following:

1. The rss component, which is implemented by RssPollingComponent class, uses customEditorConfigurer bean to parse the Date variable lastPolledDate into the specified format (yyyy/MMM/dd). lastPolledDate will be used to determine the new items added on the RSS feed.
2. The rss component periodically polls RSS feeds defined on its urlStrings property for changes. In this case rss component monitors the following RSS feeds: http://rss.cnn.com/rss/cnn_topstories.rss and http://newsrss.bbc.co.uk/rss/newsonline_uk_edition/front_page/rss.xml.
3. When an update is found, the rss component creates a normalized message that contains the new items. It then sends the normalized message to the NMR. The NMR routes the message to the trace component.
4. The trace component displays the RSS news items on the console.

Output from running Wiki MarkupOutput from running {{\[servicemix_install_dir\]\bin\servicemix servicemix.xml}}: looks like the following:

  
Loading ServiceMix from file: C:\exist\servicemix\servicemix-2.0.2\examples\http
-binding\servicemix.xml
17:34:34.768 EVENT  Starting Jetty/4.2.20RC0
17:34:34.848 EVENT  Started ServletHttpContext[/]
17:34:34.858 EVENT  Started SocketListener on 127.0.0.1:8912
17:34:34.858 EVENT  Started org.mortbay.jetty.Server@1f06dc3

Output from running Ant:

Buildfile: build.xml

init:

compile:

run:
     [echo] Running example client
     [java] <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="htt
p://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSch
ema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http:/
/schemas.xmlsoap.org/soap/encoding/" soap:encodingStyle="http://schemas.xmlsoap.
org/soap/encoding/"><soap:Body><n:getQuoteResponse xmlns:n="urn:xmethods-delayed
-quotes"><Result xsi:type="xsd:float">88.8</Result></n:getQuoteResponse></soap:B
ody></soap:Envelope>asdf

BUILD SUCCESSFUL
Total time: 6 seconds
<item>
<title>Bush supporters' cars allegedly defaced by war veteran</title>
<link>http://www.cnn.com/rssclick/2005/US/12/16/bush.vandalism.ap/index.html?sec
tion=cnn_topstories</link>
<description>Read full story for latest details.</description>
<pubDate>Sat, 17 Dec 2005 00:52:01 GMT</pubDate>
<guid isPermaLink="false">http://www.cnn.com/rssclick/2005/US/12/16/bush.vandali
sm.ap/index.html?section=cnn_topstories</guid>
</item>
<item>
<title>Stern says goodbye to terrestrial radio</title>
<link>http://www.cnn.com/rssclick/2005/SHOWBIZ/12/16/stern.last.day.ap/index.htm
l?section=cnn_topstories</link>
<description>Read full story for latest details.</description>
<pubDate>Sat, 17 Dec 2005 02:13:07 GMT</pubDate>
<guid isPermaLink="false">http://www.cnn.com/rssclick/2005/SHOWBIZ/12/16/stern.l
ast.day.ap/index.html?section=cnn_topstories</guid>
</item>

Details

The following table provides more details about the function of each component and bean in the servicemix.xml file:

Component or Bean ID	Description
jbi	jbi is the "id" of the JBI container and provides the basic infrastructure services for the following components: httpReceiver and stockQuote. During initialization, several singletons are instantiated: URLEndpoint and JBI. After initialization, the components in the JBI container are activated.
httpReceiver	This component is an HTTP server that listens at http://localhost/8912Image Removed . It forwards the message it receives from this URL to stockQuote as specified in its destinationService property in the servicemix.xml file.
stockQuote	This is a SaajBinding component that invokes an endpoint service called soapEndpoint. It is implemented by the SaajBinding class which converts an inbound JBI message into a SAAJ (Soap With Attachments for Java) request-response and sends the response back to httpReceiver. This provides a message centric way of invoking SOAP services inside providers such as Apache Axis.
soapEndpoint	A URLEndpoint object contains a URL, which is used to make connections to the remote party. A stand-alone client can pass a URLEndpoint object to the SOAPConnection method call to send a message.

Useful Code Hints

This section describes the start-up sequence and how the ServiceMix container interacts with the HTTP Binding application. The Java class files are located in the servicemix-2.0.2.jar file in the ServiceMix installation directory. To review the Java source code, unjar and decompile the .class files or download the source code.

Viewing the Java source code is recommended for understanding the information in this section.

1. The ServiceMix container reads the servicemix.xml file and instantiates the components specified through SpringJBIContainer class.
2. The container calls the afterPropertiesSet() method of the SpringJBIContainer to register the components and the activationSpecs. In this case, httpReceiver and stockQuote are registered as activationSpecs.
3. The SpringJBIContainer uses the ActivationSpec class as the container for component specific properties, such as routing information.

Some of the ActivationSpec methods are:

1. setId - takes the spring:id=jbi and sets the id of the container to "jbi"
2. setcomponentName - sets componentName to httpReceiver on first invocation and "stockQuote" in the next
3. setEndpoint - sets the endpoint properties from the servicemix.xml file
4. setService - sets the service properties from xml file
5. setDestinationService - sets the destinationService for each component

HttpConnector Details

1. The ServiceMix container reads the servicemix.xml file and to determine that it needs to instantiate a HttpConnector.
2. The container calls the init() method of HttpConnector. The init() method sets the listener's host and port property for which the HttpConnector will listen.
3. The container calls the start() method of HttpConnector. The start() method will:
   A. Add a listener object to the server property of HttpConnector.
   B. Create a new HttpContext that contains a ServletHandler class. The ServletHandler maps requests to servlets that implement the javax.servlet.http.HttpServlet API. In this case, the ServletHandler maps the request to the BindingServlet class.
   C. The server property of HttpConnector is started.

stockQuote Details

1. HttpConnector sends messages to this component as specified on its destinationService property. When this component receives a message, its onMessageExchange() method is called by the container. The onMessageExchange() method will:
   A. Create a SOAPConnection to be used in sending the message to URLEndpoint.
   B. Marshall an inbound JBI inbound into a SOAPMessage, before sending it to the URLEndpoint, as specified in the soapEndpoint property of stockQuote. A response is also requested from the URLEndpoint.
   C. The response, which is a SOAPMessage, is marshalled into a Normalized Message and is eventually sent to HttpConnector.

Related Documentation

For more information on the following topics please see:

• NMRSAAJ

• RSS

We support working with RSS and Atom via the Rome library. We support both the polling of existing RSS feeds to generate JBI messages (the example documented above) and the generation of RSS feeds from JBI messages. To see an example of how to generate RSS feeds from JBI messages go here.

For a brief explanation of the XML tags on in the servicemi.xml file, please see:

• XSD