cmoulliard

Run a Google Web Toolkit 2 project on Apache Karaf/ServiceMix

2011-12-16T15:12:00.000+01:00

To simplify the development of Web projects on Apache Karaf/Apache ServiceMix, we have created archetypes to setup WAR or WAB projects. They are very basic but they can be enriched with framework like Struts 2, Wicket, plain JSP or MyFaces JSF as they are currently supported on Apache Karaf - ServiceMix.

For the GWT users, it exists now an archetype which will create a GWT 2.4 project. To create such a project, you must generate a project from the archetype

mvn archetype:generate \
   -DarchetypeGroupId=org.ops4j.pax.web.archetypes\
   -DarchetypeArtifactId=wab-gwt-archetype \
   -DarchetypeVersion=2.0.0-SNAPSHOT \
   -DgroupId=com.mycompany \
   -DartifactId=hello \
   -Dversion=1.0

build next the WAB using hello/mvn clean install

and deploy it on Apache Karaf

Verify that the web site is well registered :

Next, you can navigate to your application in your browser and click on the button to say Hello.

Remark : A WAB project is nothing more than a WAR excepted it is packaged as a bundle file, that we have removed the WEB-INF/lib dependencies and create a MANIFEST file containing the OSGI instructions.

Apache Camel, Cxf, ActiveMQ & ServiceMix at Devoxx

2011-11-21T15:53:00.001+01:00

This year, I get the chance to present 2 talks at the Devoxx event,

one for University Talk and the other for Hands on Lab. With the help of Gert Vanthienen, we took the time to present in more detail what finally we can design as solution, architecture with Apache projects like Camel, CXF, ActiveMQ and ServiceMix and move it into a scalable, high-available platform.

That was a great challenge as this is not really easy to introduce "integration" which is not so sexy comparing to a Web Development framework, an iPhone or Android application. But times are changing and a lot of developers / architects are interested by agile approaches that we develop at Apache foundation.

With Fuse IDE tool,we can now accelerate the creation of a project using Apache Camel. The wysiwig editor and EIPs patterns allow you to quickly create new routes while the runtime editor enable to review existing project. IDE is more than a tool as it allows to run and deploy the routes in Fuse ESB, Tomcat application servers or locally. The tool is not yet finalized (release 2.1 should be available soon) but it offers a lot of possibilities to facilitate integration projects, tracing of messages (= exchanges) and investigation about time passing through the different processors.

Integration projects are moving into cloud space and this is what we have presented next with FuseSource Fabric. Fabric is not a new hype but a strategy to reduce impact of OSGI dependencies calculation, provisioning of Apache Camel routes on local, remote or cloud instances using Apache Zookeeper as registry of artefacts to be deployed (features, jars, configurations). It offers also elastic services when deploying services into the cloud.

For those who were not there, here are the links of the presentation like also the hands on lab material that we have used in the afternoon to develop a real Japa Application Project (Spring, JPA, Web) on Fuse ESB.

Presentation : http://www.slideshare.net/cmoulliard/devoxx-2011-integrationcamelcxfservicemixactivemq
Hands on Lab : https://github.com/cmoulliard/Devoxx-2011-HandsOnLab
Fusesource Fabric : http://fabric.fusesource.org/
Fusesource : Leader in Integration OpenSource

Remark : The step by guide is available on the github repo like also the skeleton (zip file)

Talks about Integration with Camel and ESB

2011-02-24T09:58:00.003+01:00

This year, I plan to make some talks about Apache ServiceMix, Apache Camel, apache ActiveMQ and show how easy it is to build integration solutions with Apache technologies.

Take free time, a two break hours and joint me during one of the following events :

Agenda

The purpose of this presentation/demo is to show you how easy it is to design integration between systems (web services, file systems, database, queue engine) using the projects Camel, ServiceMix and ActiveMQ of the foundation Apache.

First part :

Presentation of the projects Camel, ServiceMix and ActiveMq
Description of the topologies proposed : messaging, osgi, web, ...
High-availability and scalability (ServiceMix and/or ActiveMQ)

Second part :

Making of of the demo solution
Transpose it into camel DSL language
Coding of WebService (using Apache CXF), DAO and Persistence layer (Spring + Hibernate JPA) and Web layer (Apache Wicket),
Development of Camel routes,
Packaging and Deployment
Demo

Measure elapsed time with Camel

2011-02-23T18:27:00.029+01:00

With the last version of Apache Camel, we provide a event notifier support class which allow to keep information about what happen on Exchange, Route and Endpoint. One of the benefit of this class is that you can easily audit messages created in Camel Routes, collect information and report that in log by example.

When developing an application, it is very important to calculate/measure elapsed time on the platform to find which part of your code, processor or system integrated which is the bad duck and must be improved.

In three steps, I would show you How to enable this mechanism to report :
- Time elapsed to call an endpoint (could be another camel route, web service, ...)
- Time elapsed on the route exchange

STEP 1 - Create a Class implementing the EventNotifierSupport



public class AuditEventNotifier extends EventNotifierSupport {

public void notify(EventObject event) throws Exception {
  if (event instanceof ExchangeSentEvent) {
      ExchangeSentEvent sent = (ExchangeSentEvent) event;
      log.info(">>> Took " + sent.getTimeTaken() + " millis to send to external system : " + sent.getEndpoint());
  }

  if (event instanceof ExchangeCompletedEvent) {;
      ExchangeCompletedEvent exchangeCompletedEvent = (ExchangeCompletedEvent) event;
      Exchange exchange = exchangeCompletedEvent.getExchange();
      String routeId = exchange.getFromRouteId();
      Date created = ((ExchangeCompletedEvent) event).getExchange().getProperty(Exchange.CREATED_TIMESTAMP, Date.class);
      // calculate elapsed time
      Date now = new Date();
      long elapsed = now.getTime() - created.getTime();
      log.info(">>> Took " + elapsed + " millis for the exchange on the route : " + routeId);
  }
}

public boolean isEnabled(EventObject event) {
  return true;
}

protected void doStart() throws Exception {
  // filter out unwanted events
  setIgnoreCamelContextEvents(true);
  setIgnoreServiceEvents(true);
  setIgnoreRouteEvents(true);
  setIgnoreExchangeCreatedEvent(true);
  setIgnoreExchangeCompletedEvent(false);
  setIgnoreExchangeFailedEvents(true);
  setIgnoreExchangeRedeliveryEvents(true);
  setIgnoreExchangeSentEvents(false);
}

protected void doStop() throws Exception {
  // noop
}

}

Not really complicated and the code is explicit. Check the doStart() method to enable/disable the events for which you would like to gather information.

This example uses only Exchange.CREATED_TIMESTAMP property but the next version of Camel 2.7.0 will provide you the property exchange.RECEIVED_TIMESTAMP and so you will be able to calculate more easily the time spend by the exchange to call the different processors till it arrives at the end of the route.

This example collects Date information but you can imagine to use this mechanism to check if your route processes the message according to SLA, ....

STEP 2 - Instantiate the bean in Camel Spring XML


<!-- Event Notifier -->
<bean id="auditEventNotifier" class="com.sfr.audit.AuditEventNotifier">
</bean>

By adding this bean definition, Camel will automatically register it to the CamelContext created.

STEP 3 - Collect info into the log


18:10:46,060 | INFO  | tp1238469515-285 | AuditEventNotifier               | ?                                   ? | 68 - org.apache.camel.camel-core - 2.6.0.fuse-00-00 | >>> Took 3 millis for the exchange on the route : mock-HTTP-Server
18:10:46,062 | INFO  | tp2056154542-293 | AuditEventNotifier               | ?                                   ? | 68 - org.apache.camel.camel-core - 2.6.0.fuse-00-00 | >>> Took 25 millis to send to external system : Endpoint[http://localhost:9191/sis]
18:10:46,077 | INFO  | tp2056154542-293 | AuditEventNotifier               | ?                                   ? | 68 - org.apache.camel.camel-core - 2.6.0.fuse-00-00 | >>> Took 103 millis for the exchange on the route : ws-to-sis

Secure Web Services - WS-Security

2010-09-24T08:45:00.009+02:00

Security is one of the important key in the success of a IT project but most of the time only user authentication or data encryption are taken into account. So security of the application is often not adressed or leave aside due to complexity of the implementation.
One of the reason explaining this situation comes from the fact that solutions or frameworks proposed to secure an application are difficult to configure and maintain. And this remark prevalls over the specification WS-Security.

In large company having deployed WS-Services to allow intra or inter connection between applications, Web application authentication with HTTPS protocol mechanisms are use to secure platforms. That means that users discovering the credentials used to connect to the web server can potentially have access to the services of the company.

WS-Security offers a way to authenticate the user connected to a web service or allow also a user to be trusted on the web server it is connected. This mechanism is interesting because it reinforce the security but provides also a way to restrict access to unauthorized users to web services.

Apache Camel and CXF frameworks offers a simplify way to implement this with only few lines of code and spring beans definition. Let's see that in action :

STEP 1

We only need to use JAAS api to authenticate the user using the following java package "javax.security.auth.callback" and the project WS4J of Apache. Here is a simple example authenticate a user using a list and the password provided.


package org.apache.camel.example.reportincident;

import java.io.IOException;
import java.util.HashMap;
import java.util.Map;

import javax.security.auth.callback.Callback;
import javax.security.auth.callback.CallbackHandler;
import javax.security.auth.callback.UnsupportedCallbackException;

import org.apache.ws.security.WSPasswordCallback;

/**
* Callback handler to handle passwords
*/
public class UTPasswordCallback implements CallbackHandler {

  private Map passwords = new HashMap();

  public UTPasswordCallback() {
      passwords.put("claus", "sualc");
      passwords.put("charles", "selrahc");
      passwords.put("james", "semaj");
      passwords.put("abcd", "dcba");
  }

  /**
   * Here, we attempt to get the password from the private alias/passwords map.
   */
  public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException {

      String user = "";

      for (int i = 0; i < pc =" (WSPasswordCallback)" user =" pc.getIdentifier();" pass =" passwords.get(user);" string="">

STEP 2 This is here that the magic will operates as we will use Spring beans definition with Apache Web Services Framework - CXF and Apache Camel to expose the web service

Instantiate your WS4J bean

Add it as an interceptor to CXF to allow CXF to authenticate the user using the credentials provided in the SOAP header definition.

Here is an example of the SOAP header



  
      
          
              2010-09-24T07:31:06.308Z
              2010-09-24T07:36:06.308Z
          
          
              charles
              KoNvkEh9jwgvxTfcTza6+kHkKNI=
              havIKNKvlRuatlp3CncMKw==
              2010-09-24T07:31:06.306Z
          
      
  
  
      
          222
          2010-07-14
          Charles
          Moulliard
          Bla

          Bla bla

          cmoulliard@apache.org
          0011 22 33 44

And finally, declare your camel route using the web services

To play with the example, follow this example of Camel CXF and enjoy it !

Fuse Community Day - Paris - 14th of October

2010-09-23T12:18:00.003+02:00

The Fuse Community Day will take place the 14th of October in Paris. Feel free to sign up here and come to see Claus Ibsen, Guillaume Nodet, Rob Davies and myself presenting news about OSGI, SOA, Camel and ESB and some of our customers showing that in action (Lionel Cons - CERN, Cédric Bourgeois - Atos Worldwide, Jean Folly-Kpodar - Osmocom).

Parse / Format fixed length message with camel-bindy

2010-06-18T13:13:00.006+02:00

Camel-bindy which is a data formatting tool to parse / format non XML message will be enriched in the next camel release 2.4. This new version will allow to work with Fixed Length message.

A Fixed Length message as its name mention it contains data positioned at a fixed position which is by far different from Comma Separate Value format where we use a separator.

So, you will be able able to model your message like that :


   @FixedLengthRecord(length=60, paddingChar=' ')
    public static class Order {

        @DataField(pos = 1, length=2)
        private int orderNr;

        @DataField(pos = 3, length=2)
        private String clientNr;

        @DataField(pos = 5, length=9)
        private String firstName;

        @DataField(pos = 14, length=5, align="L")
        private String lastName;

        @DataField(pos = 19, length=4)
        private String instrumentCode;

        @DataField(pos = 23, length=10)
        private String instrumentNumber;

        @DataField(pos = 33, length=3)
        private String orderType;

        @DataField(pos = 36, length=5)
        private String instrumentType;

        @DataField(pos = 41, precision = 2, length=7)
        private BigDecimal amount;

        @DataField(pos = 48, length=3)
        private String currency;

        @DataField(pos = 51, length=10, pattern = "dd-MM-yyyy")
        private Date orderDate;

to parse/format the following text :

"10A9 PaulineM ISINXD12345678BUYShare2500.45USD01-08-2009"

The tool allows to add 'padding' characters and to align "LEFT" or " RIGHT" the string in the field.

More info are available on the wiki web page of camel-bindy : http://camel.apache.org/bindy.html

Run Camel route on ServiceMix 3.3.x

2010-03-30T11:22:00.006+02:00

Even if Apache ServiceMix (ESB) was mainly designed as a JBI container, it is perfectly possible to use camel routes and camel components (bindy, file, jms, ...) on this platform.

This allows by example to :
- Combine JBI binding components or Services with Camel routes,
- Use a camel component when the binding component does not exist,
- Deploy camel as Service Unit in Service Assembly

Here is a small example showing that in action. The creation of the project is very simple as you have to create a Service Unit. If you work with maven, you can use the servicemix plugin which will allow to create the maven project. Otherwise, you can create the maven structure manually.

To be able to deploy camel next, you must create a Service Assembly (= SA) who will include the Service Unit.

Don't be afraid and follow the tutorial described here for that part of the work : http://servicemix.apache.org/2-beginner-using-maven-to-develop-jbi-applications.html

When the project is ready, you create a camel-context.xml file in the directory src/main/resources. This file which is a spring xml file will contain the camel routes + beans definitions or will point to your packages if you prefer to code your routes using Camel Java DSL language instead of Spring DSL language.

Remark : in my example, I use Spring DSL language.

The route is very basic and will create a message containing the text "Hello World from SMX3!" as body value. The message is copied in an activemq queue called "in". A second route take the messages and send it to the log. The log message is readable from the console where ServiceMix 3.3.x has been started.

In the Spring file, you must add the camel bean "org.apache.camel.component.jms.JmsComponent" definition to instantiate a connection factory to the queueing engine. The broker is created and started at the launch of ServiceMix3 so you don't need to do anything else here !


       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans.xsd
       http://camel.apache.org/schema/spring
       http://camel.apache.org/schema/spring/camel-spring.xsd">

      
    
      
        
      
    
     

   
     org.apache.servicemix.samples
     
     
      
     
       Hello World from SMX3 !

To allow Camel to work with its jms component, the following dependency must be added in the pom of the camel-su.



  
    
      org.apache.camel
      camel-core
      2.2.0
    
    
      org.apache.camel
      camel-spring
      2.2.0
    
    
      org.apache.camel
      camel-jms
      2.2.0

To compile the project, simply launch the command "mvn install" to generate the SU and do the same for the SA. When the Service Assembly jar file is available, copy it in the hotdeploy directory of ServiceMix 3 server and check the log.

This example which is very basic can be extended with another camel components. In that case, don't forget to add their dependency in the SU pom as the camel lib must be added in the lib directory of the SU.

Have fun with that !

Is Webservice Reliable Messaging (WS-RM) the ugly duck of the WS-* story ?

2010-02-26T10:33:00.009+01:00

The Webservice Reliable Messaging (WS-RM) specification has been designed a couple of years ago (2005) but few projects used it. Different reasons could explain this situation, the complexity of the specification, the cost to implement it and the lack of use cases. Personally, I think that developers and architects adopt a low profile when designing a solution and spend times developing alternative solutions providing functionality similar to what WS-RM propose.

WS-RM is not a the ugly duck of the story and need more attention from community because it allows you to design solutions where you will be able to
- Guaranty of message (= web services) delivery required by example in financial order processing, alarm monitoring systems, ...
- Control the communication between the client and the server (retransmission, ...)
- Implement asynchronous solution by decoupling the request from the reply

Well, what I have presented could be assimilated to a style exercise or a faith act and you will adhere or not. To convince you about the interests to use WS-RM, I will show you How easy it is to design such a solution using Apache CXF framework. This process can be achieved in three simple steps

A. Turn on your WSDL contract into a WS-addressing

WS-addressing needs to be used because the communication between the client and server will be governed by the Reliable Message Server which is running on a different
port address number. This decoupling is required to allow to retransmit message, acknowledge the messages received and guaranty the delivery

Here is one way that you can adopt :

the other consists in to use a Policy Rule (= WS-Policy)

B. Activate the Reliable Server

Now that the WSDL contract is modified, we need to add the Reliable Server to the configuration of our platform. I will show you using a spring xml configuration file
but you can use the Apache CXF classes in your java code if you want

To activate the RM server, you simply needs to add the tags wsa:addressing and wsrm-mgr in the bus definition of Apache CXF. Different parameters are available like
retransmission interval, acknowledge interval. I will not digg into these ones and if you need information, I invite you to check Apache CXF javadoc and specifications. By example
ikt is possible to activate also the persistence manager of the RM server ;-)

If you use CXF in combination with the Routing engine Apache Camel, you don't need to do additional things as the Apache CXF endpoint who will consume the web servicesmessages
will be drived by the RM server of CXF.

Here is an example of Camel integration with CXF


  
  
  

  
  
      
           // messages are consumed from CXF endpoint
           // the body of the WS message is converted directly into a POJOI
           // We call a POJO to save the reportincident in a DB
           // We put the object in a queue
          
               // We provide a feedback message as the WS is of type request/replyt

C. Verify

If you use a java client using Apache CXF java classes, you can easily enable the logging of the IN/OUT WS messages exchanged with the RM server and the application.
The following trace shows that :
- a sequence has been started
- each message is identified '' with a UID
- Within a sequence, the messages send receive a messageID
- The server acknowledge the reception (= processing) of the messages

>>>> Invoking reportIncident ... for accident : 0 24-fÚvr.-2010 9:48:39 org.apache.cxf.transport.http.HTTPConduit setUpDecoupledDestination INFO: creating decoupled endpoint: http://localhost:9999/camel-example/incident 2010-02-24 09:48:39.796::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2010-02-24 09:48:39.828::INFO: jetty-6.1.21 2010-02-24 09:48:39.921::INFO: Started SelectChannelConnector@localhost:9999 24-fÚvr.-2010 9:48:40 org.apache.cxf.ws.rm.Proxy invoke INFO: Sending out-of-band RM protocol message {http://schemas.xmlsoap.org/ws/2005/02/rm}CreateSequence. 24-fÚvr.-2010 9:48:41 org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose INFO: Outbound Message --------------------------- ID: 1 Address: http://localhost:8080/cxf/camel-example/incident Encoding: UTF-8 Content-Type: text/xml Headers: {SOAPAction=["http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"], Connection=[Keep-Alive], Accept=[*/*]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:508b8914-1621-4992-ae2d-2249d417069a</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/cxf/camel-example/incident</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://localhost:9999/camel-example/incident</address> </replyto> </soap:header> <soap:body> <createsequence xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm" ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <acksto> <ns2:address>http://localhost:9999/camel-example/incident</ns2:address> </acksto> <expires>PT0S</expires> <offer> <identifier>urn:uuid:b12e4ccf-3bec-4f76-85f6-2b64f24745b5</identifier> <expires>PT0S</expires> </offer> </createsequence> </soap:body> </soap:envelope> -------------------------------------- 24-fÚvr.-2010 9:48:41 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 1 Response-Code: 202 Encoding: UTF-8 Content-Type: text/xml; charset=utf-8 Headers: {content-type=[text/xml; charset=utf-8], Content-Length=[532], Server=[Jetty(6.1.x)]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> urn:uuid:73d86df6-7d45-42df-8008-2a4ca48682fd </messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/none</address> </replyto> </soap:header> <soap:body> </soap:body> -------------------------------------- 24-fÚvr.-2010 9:48:41 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 2 Address: /camel-example/incident Response-Code: 200 Encoding: UTF-8 Content-Type: text/xml; charset=UTF-8 Headers: {content-type=[text/xml; charset=UTF-8], connection=[keep-alive], Host=[localhost:9999], Content-Length=[1006], User-Agent=[Progress FUSE Services Fram ework 2.2.6-fuse-01-00], Content-Type=[text/xml; charset=UTF-8], Accept=[*/*], Pragma=[no-cache], Cache-Control=[no-cache]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> urn:uuid:c8e59735-7738-40b2-98c1-28be15274b35 </messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:9999/camel-example/incident</to> <relatesto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:508b8914-1621-4992-ae2d-2249d417069a</relatesto> </soap:header> <soap:body> <createsequenceresponse xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm" ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <identifier>urn:uuid:b35dff50-43cb-43ad-9c9e-4b59f7cb55e7</identifier> <expires>P0Y0M0DT0H0M0.0S</expires> <accept> <acksto> <ns2:address>http://localhost:8080/cxf/camel-example/incident</ns2:address> </acksto> </accept> </createsequenceresponse> </soap:body> </soap:envelope> -------------------------------------- 24-fÚvr.-2010 9:48:41 org.apache.cxf.ws.rm.soap.RMSoapInterceptor updateServiceModelInfo INFO: Updating service model info in exchange 24-fÚvr.-2010 9:48:41 org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose INFO: Outbound Message --------------------------- ID: 3 Address: http://localhost:8080/cxf/camel-example/incident Encoding: UTF-8 Content-Type: text/xml Headers: {SOAPAction=["http://reportincident.example.camel.apache.org/ReportIncident"], Connection=[Keep-Alive], Accept=[*/*]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://reportincident.example.camel.apache.org/ReportIncident</action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:85a1ebac-5293-4daa-a656-987967aa2a4d</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/cxf/camel-example/incident</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://localhost:9999/camel-example/incident</address> </replyto> <wsrm:sequence ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"> <wsrm:identifier>urn:uuid:b35dff50-43cb-43ad-9c9e-4b59f7cb55e7</wsrm:identifier> <wsrm:messagenumber>1</wsrm:messagenumber> </wsrm:sequence> </soap:header> <soap:body> <ns2:inputreportincident ns2="http://reportincident.example.camel.apache.org"> <incidentid>0</incidentid> <incidentdate>29-04-2009</incidentdate> <givenname>moulliard</givenname> <familyname>charles</familyname> <summary> This is a web service incident</summary> <details>This is a web service incident - details</details> <email>cmoulliard@gmail.com</email> <phone> +222 10 50 22 </phone> </ns2:inputreportincident> </soap:body> </soap:envelope> -------------------------------------- 24-fÚvr.-2010 9:48:41 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 3 Response-Code: 202 Encoding: UTF-8 Content-Type: text/xml; charset=utf-8 Headers: {content-type=[text/xml; charset=utf-8], Content-Length=[532], Server=[Jetty(6.1.x)]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> urn:uuid:37dceb90-e1f5-4014-9749-8d4ae7eebb13</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/none</address> </replyto> </soap:header> <soap:body> </soap:body> -------------------------------------- 2010-02-24 09:48:41.937::INFO: seeing JVM BUG(s) - cancelling interestOps==0 24-fÚvr.-2010 9:48:42 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 4 Address: /camel-example/incident Response-Code: 200 Encoding: UTF-8 Content-Type: text/xml; charset=UTF-8 Headers: {content-type=[text/xml; charset=UTF-8], connection=[keep-alive], Host=[localhost:9999], Content-Length=[1057], User-Agent=[Progress FUSE Services Fram ework 2.2.6-fuse-01-00], Content-Type=[text/xml; charset=UTF-8], Accept=[*/*], Pragma=[no-cache], Cache-Control=[no-cache]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://reportincident.example.camel.apache.org/ReportIncidentEndpoint/ReportIncidentResponse</action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:6163b07e-c983-47f7-8699-c4670b61a213</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:9999/camel-example/incident</to> <relatesto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:85a1ebac-5293-4daa-a656-987967aa2a4d</relatesto> <wsrm:sequence ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"> <wsrm:identifier>urn:uuid:b12e4ccf-3bec-4f76-85f6-2b64f24745b5</wsrm:identifier> <wsrm:messagenumber>1</wsrm:messagenumber> </wsrm:sequence> </soap:header> <soap:body> <ns2:outputreportincident ns2="http://reportincident.example.camel.apache.org"> <code>OK</code> </ns2:outputreportincident> </soap:body> </soap:envelope> -------------------------------------- >>>> Result - code : OK 24-fÚvr.-2010 9:48:43 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 5 Address: /camel-example/incident Response-Code: 200 Encoding: UTF-8 Content-Type: text/xml; charset=UTF-8 Headers: {content-type=[text/xml; charset=UTF-8], connection=[keep-alive], Host=[localhost:9999], Content-Length=[955], SOAPAction=["http://schemas.xmlsoap.org/ ws/2005/02/rm/SequenceAcknowledgement"], User-Agent=[Progress FUSE Services Framework 2.2.6-fuse-01-00], Content-Type=[text/xml; charset=UTF-8], Accept=[*/*], P ragma=[no-cache], Cache-Control=[no-cache]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement </action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:f57c0b96-fcc3-4543-bbc3-fd15a54622e7</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:9999/camel-example/incident</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/none</address> </replyto> <wsrm:sequenceacknowledgement ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"> <wsrm:identifier>urn:uuid:b35dff50-43cb-43ad-9c9e-4b59f7cb55e7</wsrm:identifier> <wsrm:acknowledgementrange lower="1" upper="1"> </wsrm:acknowledgementrange> </wsrm:sequenceacknowledgement> <soap:body> </soap:body> -------------------------------------- 24-fÚvr.-2010 9:48:43 org.apache.cxf.ws.rm.soap.RMSoapInterceptor updateServiceModelInfo INFO: Updating service model info in exchange 24-fÚvr.-2010 9:48:44 org.apache.cxf.ws.rm.Proxy invoke INFO: Sending out-of-band RM protocol message {http://schemas.xmlsoap.org/ws/2005/02/rm}SequenceAcknowledgement. 24-fÚvr.-2010 9:48:44 org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose INFO: Outbound Message --------------------------- ID: 6 Address: http://localhost:8080/cxf/camel-example/incident Encoding: UTF-8 Content-Type: text/xml Headers: {SOAPAction=["http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement"], Connection=[Keep-Alive], Accept=[*/*]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement</action> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">urn:uuid:c5584570-c10f-49cc-a3ef-c2c53363ec66</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://localhost:8080/cxf/camel-example/incident</to> <replyto lns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/none</address> </replyto> <wsrm:sequenceacknowledgement ns2="http://schemas.xmlsoap.org/ws/2004/08/addressing" wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm"> <wsrm:identifier>urn:uuid:b12e4ccf-3bec-4f76-85f6-2b64f24745b5</wsrm:identifier> <wsrm:acknowledgementrange lower="1" upper="1"> </wsrm:acknowledgementrange> </wsrm:sequenceacknowledgement> <soap:body> </soap:body> -------------------------------------- 24-fÚvr.-2010 9:48:44 org.apache.cxf.interceptor.LoggingInInterceptor logging INFO: Inbound Message ---------------------------- ID: 6 Response-Code: 202 Encoding: UTF-8 Content-Type: text/xml; charset=utf-8 Headers: {content-type=[text/xml; charset=utf-8], Content-Length=[532], Server=[Jetty(6.1.x)]} Payload: <soap:envelope soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:header> <messageid xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> urn:uuid:786ad464-fb01-452a-9036-63c383955133</messageid> <to xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</to> <replyto xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"> <address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/none</address> </replyto> </soap:header> <soap:body> </soap:body> -------------------------------------- 24-fÚvr.-2010 9:49:12 org.apache.cxf.transport.http_jetty.JettyHTTPServerEngine shutdown </soap:envelope></soap:header></soap:envelope></soap:header></soap:envelope></soap:envelope></soap:envelope>

Conclusion

Awesome, isn'it. Even, if you continue to doubt about this specification, I'm pretty sure that in the future you will take it into account into your decision process regarding
to what has been developed here.

New features for Apache Camel Bindy (non XML binding framework)

2009-11-20T16:55:00.002+01:00

Today has been a very productive day. I have found the time to update the documentation about the Apache Camel Tutorial on OSGI and commit the last new features added to camel-bindy : the non XML binding framework used to parse or generate CSV, FIX, ... messages

This new version of bindy includes important new features like :
- Required (@DataField) to check mandatory field
- Position (@DataField and @KeyValuePairField) when the CSV/FIX message to be generate contain fields which are placed at a different position then those used to parse it
- Section which allow to define the class containing by example the header, body or footer section

and

- OneToMany which allow to :

Read a FIX message containing repetitive groups (= group of tags/keys)
Generate a CSV with repetitive data

More info can be find here.

LangDetecten>fr YahooC

OSGI

Tutorial part 1 about Apache Camel and OSGI (reviewed)

2009-11-02T12:36:00.004+01:00

Last friday, I have spend some times to update the part 1 of the Apache Camel tutotrial. This tutorial shows how you can easily and quickly build and deploy a small SOA project using Camel 2.0 top of Apache Felix Karaf 1.0.0

The second part of this tutorial will be upgraded soon and will include a new section about integration tests with Pax Exam

Apache Camel Group on Linkedln

2009-11-02T12:33:00.005+01:00

Apache Camel has now its Group on Linkedln web site : http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

Feel free to join us to discuss / exchange ideas / news and jobs about your favorite mediation and router framework

Building OSGi applications with the Blueprint Container specification

2009-10-28T10:21:00.002+01:00

Jarek Gawor which is an advisory software engineer for IBM and an Apache Geronimo committer /PMC member has published an interesting article on :

Building OSGi applications with the Blueprint Container specification

Fuse Community Day - Paris - 1st October

2009-09-16T13:44:00.004+02:00

The first "Fuse Community day" will take place the 1st October 2009 in Paris. Different topics will be presented by the founders James Strachan, Rob Davies, Guillaume Nodet of the projects Apache Camel, ActiveMq and Karaf during this day.

To join the day, please register on this site : http://form.fusesource.com/forms/registerforParisDay

Here is the agenda :

09:30 - Réception et petit-déjeuner

10:00 - Ouverture de la conférence par Magali Briol

10:15 - FUSE et OSGi par Guillaume Nodet; Membre PMC

- “La technologie OSGi est au coeurs des produits FUSE. Cette présentation vous permettra de découvrir OSGi, Apache Karaf, et leur utilisation au sein de FUSE ESB.“

11:00 - Enterprise Apache ActiveMQ par Rob Davies; Membre PMC et Co-fondateur

- “Apache ActiveMQ is a the most widely used open source messaging system to date.

This presentation will look at deploying Apache ActiveMQ in the enterprise - for high availibity,

across wide area networks and how to tune Apache ActiveMQ to for performance

and scalability.“

11:45 - Cas client par Sylvain Thomas; Architecte Capgemini

- “Recueil de données satellites via FUSE ESB. Mise à disposition de Géo localisations et de

données règlementaires.“

12:30 - Déjeuner

13:30 - Intégration avec Apache Camel par James Strachan; Membre PMC et Co-fondateur

- “Apache Camel is a powerful open source integration framework based on Enterprise Integration Patterns with Beans Integration. This presentation will give an overview of Apache Camel and how to implement Enterprise Integration Pattern to solve a number of integration issues.“

14:15 - Camel 2.0 et le développement de solutions orientées entreprise par

Charles Moulliard; Apache Camel Committer et Senior Enterprise Architecte

- “Cette présentation va vous donner un aperçu des nouvelles fonctionnalités de Camel 2.0 et comment celles-ci vont aider les architectes/développeurs à construire des solutions orientées entreprises dans un environnement OSGI.“

15:00 - Pause Café

15:15 - Intégrer JBI et OSGi avec ServiceMix4, JBI Components nouvelles caractéristiques et

roadmap par Jean-Baptiste Onofré ; ServiceMix Commiter

- “Présentation des différentes versions de ServiceMix. Modularité au sein de ServiceMix4 (kernel

Karaf, NMR, composants). Publication de WSDL pour facilité l'utilisation des composants.“

16:00 - Introduction à FUSE Integration Designer par James Strachan et Rob Davies

- “FUSE Integration Designer is an Eclipse tool design to help you create, debug and deploy your integration solutions for Apache Camel, ServiceMix and ActiveMQ.“

16:30 - Fermeture de la conférence

Don't Use System.out.println! but Log4j

2009-06-26T10:10:00.000+02:00

Here is the bible when you want/need to configure Log4J. Thanks to Vipan Singla

Don't Use System.out.println!

OSGi Blueprint Services

2009-06-24T12:25:00.002+02:00

In this very nice presentation of Guillaume Nodet, you will discovered what is magic behind OSGi Blueprint Services. This implementation who will be part of the next OSGI specification 4.2 will help the Java developer/architect to better design their solutions. The blueprint services are largely inspired from Spring Dynamic Module project but now it becomes a standard like EJB, ... in the past.

OSGi Blueprint Services

View more Microsoft Word documents from gnodet.

Apache Camel / OSGI / Wicket (real example - tutorial part2)

2009-05-05T13:44:00.004+02:00

I have finalized a first draft of the second part of my tutorial about Camel 2.0 / ServiceMix-Karaf / CXF / OSGI / Apache Wicket

The purpose of the second part was to explain how to design a simple project where different concepts like :

persistence (Hibernate/spring),
routing (Apache Camel 2.0),
mapping between CSV file and objects (using camel-bindy),
webservices (Apache CXF - OSGI),
osgi stuffs,
packaging and deployment on Apache Karaf/ServiceMix OSGI server (features, PAX url),
web application integration (Apache Wicket, PAX Web)

have been addressed.

The tutorial has been designed in 4 parts :

Part 2a : real example, architecture, project setup, database creation
Part 2b : transform projects in bundles
Part 2c : add infrastructure and routing
Part 2d : web and deployment

and is available here : http://cwiki.apache.org/CAMEL/tutorial-osgi-camel-part2.html

Don't hesitate to provide me your remarks/comments to improve it.

Trick to pass an uri declared in a property file to a Camel route

2009-05-05T13:26:00.005+02:00

Defining Camel uris in a file is not so easy. Until now, the only possibility was to create a camel endpoint where the uri was declared in the XML file.

Here is a trick who will simplify your life to declare/define the uri in a property file. Spring injection is used to replaced the variable declared in your XML file with the value discovered in the property file.

By example, to work with the following uri : file://d:/temp/data/?move=d:/temp/done/${file.name}

Remark : as you can see, the uri contains a variable to a Camel variable and in consequence is not a Spring bean. So we have to inform Spring that the variable to be searched in the XML file use another syntax delimiter (#{} instead of ${}).

Here is what you have to do

Step 1 : Create org.springframework.beans.factory.config.PropertyPlaceholderConfigurer bean

Define a PropertyPlaceHolder (using another prefix/suffix delimiter) to avoid conflict between your camel variable and Spring property

(1) : Define a different prefix instead of ${ which is the value by default and used as variable
(2) : Define the value of the suffix. In this case, this is the same as the default value

Step 2 : Create org.apache.camel.example.reportincident.routing.properties

Create the following file : org.apache.camel.example.reportincident.routing.properties and put it in your classpath. If you plan to deploy your camel route under Apache ServiceMix Kernel --> Apache Karaf, add this file in the META-INF/spring directory by example
Add the following property :

uriFile=file://d:/temp/data/?move=d:/temp/done/${file.name}

Step 3 : Create an endpoint in your Camel Spring DSL file

Create a camel endpoint for the uri that you would like to use

(1)

(1) As you can see, we use as a Spring variable reference the syntax #{} so spring will retrieve the value from the variable declared in the file

Step 4 : Adapt your route

Define the uri of your route like this :

Cool isn't !!

Camel Tutorial - OSGI part 1 (UPDATED)

2009-04-22T10:21:00.004+02:00

I'm currently working on the part of the camel - OSGI tutorial part 2 but I have found the time to update the first part. This was required because I would like to use the maven PAX plugin instead of spring maven plugin and test it against SMX 1.1.0 and Camel 1.6.0.

The PAX maven plugin offers a lot of advantages regarding to the one of Spring (which is currently becoming a new tool called - bundlor)
- pom.xml file generated only include dependencies, plugin required,
- project can be designed with several modules,
- project can be tested with PAX Exam and launched using PAX runner
- ...

Here is the link to tutorial

Distributed OSGi – A Simple Example

2009-04-21T14:42:00.002+02:00

Here is a very interesting article explaining what Distributed OSGI will looks like using implementation done by CXF project.

<coderthoughts />: Distributed OSGi – A Simple Example

ServiceMix 4 et son kernel OSGi (Xebia France)

2009-04-20T12:54:00.003+02:00

L' excellente revue Xebia parle de ServiceMix et Service Mix Kernel.

Il est toujours intéressant de constater que des acteurs importants dans la vulgarisation des technologies clés dans les développements Java, ESB s'intéressent à ce projet inovateur, construit sur des fondations solides : Apache Felix, Spring DM et PAX et continue à séduire.

The power of Apache wicket and Spring OSGI Service top of ServiceMix 4

2009-04-14T15:13:00.026+02:00

In a previous post, I have explained how you can transform ServiceMix 4 as a Web Application Server. In this new post, I will show you How you can combine the power of Apache Wicket and Spring OSGI services together on ServiceMix 4 with the help of PAX Web.

This mix can be achieved very easily. Only a few steps are required.

1) Create a maven project where you will design your spring service and expose it as an OSGI service according to the Spring documentation.

2) Create a new maven project that you will use to package your Apache web application. The trick here is to modify your web.xml file like this :

a) add listener and context parameter for the Spring OSGI Context Loader

b) Add Spring Factory to Apache (required to allow injection of dependency in java classes of Wicket)

Please refer to the Apache Wicket Web site for more info about Spring integration

3) create an applicationContext.xml file under WEB-INF folder containing the reference to the OSGI service :

<osgi:reference id="incidentService" interface="org.apache.camel.example.reportincident.service.IncidentService"/>

4) And of course, in your Wicket page, inject dependency using the Wicket annotation :

@SpringBean
private IncidentService incidentService;

5) Now generate the bundles (JAR/WAR) and deploy them top of SMX4. Before to deploy the war containing the web project, verify that the following bundles are deployed on SMX4 :

- OPS4J Pax Web - Web Container (0.6.0)
- OPS4J Pax Web - Jsp Support (0.6.0)
- OPS4J Pax Web Extender - WAR (0.5.1)
- OPS4J Pax Web Extender - Whiteboard (0.5.1)
- OPS4J Pax Url - war:, war-i: (0.4.0)

- spring-osgi-web (1.2.0.rc1)
- Wicket (1.3.5)
- Wicket IoC common code (1.3.5)
- Wicket Spring Integration (1.3.5)
- Wicket Spring Integration through Annotations (1.3.5)
- Wicket Extensions (1.3.5)

- Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.1)

A tutorial will be published soon with material and step by step.

Remarks :
- PAX-runner can be used as running environment (instead of Servicemix) with Equinox, Felix, ...
- Many thanks to Alin Dreghiciu (PAX project) for its help/support

What's new in ServiceMix 4

2009-03-31T12:20:00.004+02:00

Rob Biresch has published an interesting post in dzone (SOA zone) about what is new in ServiceMix 4.

For more info, read its post and don't hesitate to vote on dzone

http://soa.dzone.com/news/whats-new-servicemix-4x

Trick to customize war deployment on ServiceMix4 using PAX

2009-03-30T15:40:00.006+02:00

Here is another very interesting trick that you can use to customize the war the deployment process on ServiceMix.

customize = in this context, this word means How can I add property or extend existing of a MANIFEST file

e.g. : The WAR to be deployed contains tlb files created under the folder WEB-INF/tags/form and WEB-INF/tags/jms. By default PAX will create a MANIFEST file containing the property Bundle-Classpath with :

WEB-INF/classes
all jars from WEB-INF/lib directory

but will not take care about your folders

Two possibilities are available to tell to PAX that it must include in the Bundle-Classpath your folders

1) Command + uri

This one consists in to pass the parameters as an uri like this :

install war:file:///d:/temp/activemq-web-console-5.2.0.war?Bundle-Classpath= ., WEB-INF/tags/form, WEB-INF/tags/jms&Webapp-Context= activemqweb

2) Create a file.bnd + command

Another interesting option is to provide as a file the location of the WAR and the properties that you want to add

Create a file called xxxx.bnd
Add in the file the following lines :

WAR-URL=file:///c/temp/activemq-web-console-5.2.0.war
Bundle-Classpath=., WEB-INF/tags/form, WEB-INF/tags/jms
Webapp-Context=activemqweb

use in your favorite OSGI server (ServiceMix) the following command to install the WAR :

install war-i:file:///c:/temp/activemq-web-console-5.2.0.bnd

ServiceMix 4 as a Web Application Server

2009-03-27T14:16:00.007+01:00

This week, I have discovered the web possibilities offered by the ServiceMix 4 platform. SMX ("pour les intimes") uses as its core platform the excellent packages of the project PAX which is the umbrella project for all OSGi bundles and tools.

In standard, the following bundles are installed :

[ 9] [Active ] [ ] [ 8] OPS4J Pax Logging - API (1.3.0)
[ 10] [Active ] [ ] [ 8] OPS4J Pax Logging - Service (1.3.0)
[ 11] [Active ] [ ] [ 5] OPS4J Pax Url - wrap: (0.3.3)
[ 12] [Active ] [ ] [ 5] OPS4J Pax Url - mvn: (0.3.3)

They are used to log information of the server and to install or wrap bundles. Nevertheless, PAX project is not limited to the mentioned bundles but proposes also Web support for jetty.

To install or transform ServiceMix as a Web Application Server, you can use the "web" and "web-core" feature (available under ServiceMix 4) or install the following bundles manually :

- OPS4J Pax Web - Web Container (0.5.2)
- OPS4J Pax Web - Jsp Support (0.5.2)
- OPS4J Pax Web Extender - WAR (0.5.0)
- OPS4J Pax Web Extender - Whiteboard (0.5.0)
- OPS4J Pax Url - war:, war-i: (0.3.3)
- Apache ServiceMix Bundles: jetty-6.1.14 (6.1.14.1)

The Web Application Server becomes available at the url http://localhost:8080.

Evidently, no jsp pages, servlets are available. Don't worry, to deploy a WAR, you only have to copy it to the deploy directory of ServiceMix and it will convert be converted as a bundle

By example, you can install a simple Hello World war using the command

install war:file:///d:/temp/sample.war?Webapp-Context=sample

remarks :
- file:/// must be changed according to the location of your war
- The parameter WebApp-Context is added to have a nicer web address

and see the result at the address : http://localhost:8080/sample/index.html

Yes, this looks beautiful but the web port number is 8080, my boss would like to secure the web site, change the session timeout, ....

This is very simple to do, you create a file named (org.ops4j.pax.web.cfg) and copy it in the directory etc of servicemix, in this file you can parametrize by example the following properties (see PAX for more information) :

org.osgi.service.http.port=80
org.ops4j.pax.web.session.timeout=10

You restart Servicemix and now the web site is available at the following address :

http://localhost/sample/index.html

Can Apache Camel be independent of the queuing engine ?

2009-03-17T12:32:00.014+01:00

Designing and deploying an Apache Camel project in an environment where you have (as an administrator) the control is something very simple to do. Most of the time, the code that you will receive from the developers will be ready to be deployed on the server (ServiceMix, J2EE, ...).

But this is not the case, when you work in big companies where the infrastructure is separated from the teams in charge to design/build/deploy and release the application. As a developer you don't have access to the acceptance or production environment. This means that you must provide different configuration files to the builder team and/or release management in order to deploy your application in development, acceptance and production environment.

Obviously, the name of the servers are not the same and the infrastructure is in charge to manage the queues servers. In this environment, infra will never accept that the queues definition or creation of the queuing engine are under the responsibility of the developer(s). Thus, it will not be possible in your spring DSL file (or Camel Java DSL classes) to declare your queuing engine like this :

<bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent" >
<property name="brokerURL" value="vm://localhost:61616" / >
</bean >

remark: vm://localhost:61616 must be changed to serverName.intranet.domainName:port
depending on queuing engine deployed in the different environment.

To make Camel independent of its queuing engine :

ActiveMq,
WebSphereMQ,
SonicMq,
TIBCO,
...

and parameters like :

Size of the queue,
Size of the messages accepted on the queue,
Persistence of the messages
...

you must made different modifications. Let's assume that you plan to use ActiveMq as your queuing engine. Here is the list of the modifications to do :

1) Add the required bundles to your ServiceMix 4 osgi server to allow it to work with ActiveMq. Normally, the features transaction and activemq are activated by default in the file etc/org.apache.servicemix.features.cfg. So, you don't have to do anything else except if you use ServiceMix Kernel. In this case, you have to add the bundles manually or add a link (in the config file) to the features.xml file where the bundles have been declared

2) Create a spring xml file where the parameters of the queuing engine are defined. Luckily, such a file already exists and is available from Apache ServiceMix 4 project. So, copy the file into the deploy folder of ServiceMix 4 or Servicemix 4 Kernel

3) Create a osgi-queueservice.xml file containing the following lines and copy it in the deploy folder of ServiceMix

<?xml version="1.0" encoding="UTF-8"? >
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:osgi="http://www.springframework.org/schema/osgi"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd">

<bean id="active-mq" class="org.apache.activemq.camel.component.ActiveMQComponent" />

<osgi:service id="osgiqueuingservice" ref="active-mq" interface="org.apache.camel.Component"/>

</beans>

When the spring file will be at the server startup loaded by Spring (though its Application context), it will create the bean "active-mq" and instantiate the class : org.apache.activemq.camel.component.ActiveMQComponent.

Remarks :
- No parameters are provided to the ActiveMqComponent like brokerUrl, ...
- If you need to work with another JMS queuing engine, you can replace the class ActiveMQComponent by : org.apache.camel.component.jms.JmsComponent

Next it will create an OSGI service called "osgiqueuingservice" and expose it through the interfaces : org.apache.camel.Component

Remark : As JmsComponent, ActiveMqComponent implements this interface, the OSGI service is generic. So you could parameterized it using a property file (cfg file in the ServiceMix world)

4) The last step is very simple. In your camel config file, you add a reference to your osgi service in order to retrieve the queuing engine like this :

<osgi:reference id="queuingservice" interface="org.apache.camel.Component" />

Please remark that you import the Component interface. So, Camel becomes independent of the queuing engine used (WebSphere, TIBCO, ActiveMQ, ...)

and in your Camel route :

<camel:from uri="queuingservice:queue:in" />

How to share connection pool - OSGI- SMX4

2009-03-11T10:56:00.004+01:00

Here is an interesting article published on the blog of Adrian Tranaman showing How to share a connection pool between OSGI bundle.

How to create OSGI bundles using PAX scripts

2009-01-09T10:48:00.004+01:00

This following article(s) started to explore how PAX (see here for more information on PAX : http://wiki.ops4j.org/display/ops4j/Pax) scripts can be used with (or without) Spring DM
and help developer life to

create/modify OSGI bundles
deploy them in Equinox/Felix/...

How to create a Spring-DM bundle using PAX scripts - JQuantLib

http://aslamkhan.net/software-development/osgi-cookbook-1-a-simple-bean/

Tutorial introducing How to create, design a simple SOA solution using Camel and OSGI

2008-12-09T11:49:00.003+01:00

After a few weeks of investigation about OSGI, I have decided to start to write a tutorial showing How we can design/create a Service Oriented Architecture using Camel in combination with OSGI standard. The first part of this tutorial has been published and next part will come soon.

Through this tutorial, the user will see how such a solution can be designed and deployed in two really interesting products : ServiceMix Kernel server (based on Apache Felix) and Spring Dynamic Server (based on Eclipse Equinox).

Link : http://cwiki.apache.org/confluence/display/CAMEL/tutorial-osgi-camel-part1

Charles Moulliard's Weblog

2008-10-03T13:30:00.003+02:00

Web site related interested link :

Spring Dynamic Modules Tutorial - Tutorial for Spring Dynamic Modules (DM) for OSGi™ Service Platforms

Charles Moulliard's Weblog

2008-09-23T15:32:00.007+02:00

Web service related links of interest this week:

Glen Mazza's Weblog: "Creating a WSDL-first web service with Apache CXF or GlassFish Metro"
Enterprise Mashup Services :This is the second part of the "Enterprise Mashup services" article explaining how to use JSF and AJAX instead of javascript in JSP page
SOA - Enterprise Mashup Services: This interesting article shows How we can design SOA solutions in enterprise world by leveraging J2EE platform and using Java to JavaScript API, Google Map, DWR & Spring
Why Mashups = (REST + ‘Traditional SOA’) * Web 2.0 - Blog the web :
A Mashup is a new service, that combines functionality or content from existing sources. These existing sources can be Web Services (through the use of API’s), RSS feeds or even just other Websites (by screen-scraping).

Taking Apache Camel for a ride (ApacheCon 11/05/2008)

2008-08-08T16:07:00.003+02:00

From: bruce.snyder, 3 months ago

Takingapachecamelforaride

View SlideShare presentation (tags: apachecon eu)

Presentation from ApacheCon EU 2008

SlideShare Link

Design Patterns Quick Reference

2008-08-08T10:55:00.005+02:00

Thanks to Mark to spend time to compile in pdf document the famous GoF patterns

http://www.mcdonaldland.info/2007/11/28/40/

Getting Started with OSGi

2008-08-08T10:31:00.004+02:00

Here are interesting links to start to work on OSGI :

1) Neil Bartlett : http://neilbartlett.name/blog/osgi-articles/
2) Osgi for beginners (Serverside): http://www.theserverside.com/tt/articles/article.tss?l=OSGiforBeginners
3) JavaWorld :
- Part1 : http://www.javaworld.com/javaworld/jw-03-2008/jw-03-osgi1.html
- Part2 : http://www.javaworld.com/javaworld/jw-04-2008/jw-04-osgi2.html
- Part3 : http://www.javaworld.com/javaworld/jw-06-2008/jw-06-osgi3.html
4) Spring Dynamics Module : http://www.springframework.org/osgi/demos
5) Apache Felix : http://felix.apache.org/site/tutorials-examples-and-presentations.html

Choosing between Routing and Orchestration in an ESB

2008-08-08T10:15:00.002+02:00

The goal of this interesting article is to help ESB users choose the right answer according to their needs, when confronted with the most complex and diverse of ESB concepts: routing and orchestration.

Instead of abstract theorizing we will ground our efforts and reasoning in simple, real-world examples in an attempt to fill the void between low-level routing and global, business service orchestration. In other words: We will try to uncover how the different layers of routing and orchestration build up.

Even if the solution used to make the design is a ESB based on JBI specification --> Petals, the publication provides a clear presentation of the concepts and help the architect to choose.

Link : Choosing between Routing and Orchestration in an ESB

Apache Camel 1.4 released

2008-08-07T17:05:00.001+02:00

The new version of the Enterprise Service Bus (ESB) Apache Camel ( 1.4.0 ) has been released. This release includes 261 new features, improvements and bug fixes. With this release, Camel proves that they become a significant actor in the SOA world. The community behind and the talented developers help this project to grow fast and to provide interesting alternatives to design SOA solutions around Enterprise Integration Patterns and the DSL language.