To make bundle of camel context as EIP as well as mediation router, by:

Configuring camel-context.xml

We can use Java DSL or Spring XML-based syntax for specifying routes and will probably support things like a Groovy DSL in the future as well. If you look at the src/main/resources/camel-context.xml file inside the tutorial-camel-su project, you will see how the Maven archetype already generates an example of the XML syntax.

To use Java DSL, we change this file to point to the package that will contain our RouteBuilder classes. When the SU is started, all RouteBuilder classes will be located and the routes in there will be activated.


<beans ...>

…

<camelContext id=”camel” xmlns=”http://activemq.apache.org/camel/schema/spring”>

<package>org.apache.servicemix.tutorial.camel</package>

</camelContext>

…

</beans>

To use Spring configuration, we can use something like

<beans …>

…

<camelContext id=”camel” xmlns=”http://activemq.apache.org/camel/schema/spring”>

<route>

<from uri=”file:/env/sandbox/file-from” />

<to uri=”file:/env/sandbox/file-to” />

</route>

</camelContext>

…

</beans>

We are going to create 3 Maven projects:

• a servicemix-camel SU project
• a servicemix SA project
• a parent project to hold the previous two

Create the parent project

Start by creating a new directory to hold your project. Add a pom.xml file to it:

<?xml version="1.0" encoding="utf-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.servicemix.tutorial.camel</groupId>
  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>
  <name>SMX-Camel :: Tutorial</name>
  <url>http://servicemix.apache.org</url>
</project>

Create the servicemix-camel SU project

Use the servicemix-camel-service-unit Maven archetype to create a first SU project inside the parent directory:

mvn archetype:create -DarchetypeArtifactId=servicemix-camel-service-unit \
-DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-su

Create the SA project and add the SU

Use the servicemix-service-assembly Maven archetype to create the SA project:

mvn archetype:create -DarchetypeArtifactId=servicemix-service-assembly \
-DarchetypeGroupId=org.apache.servicemix.tooling -DartifactId=tutorial-camel-sa

Don’t forget to add the SU as a dependency to the SA’s pom.xml:

<project>
  ...
  <dependencies>
    <dependency>
      <groupId>org.apache.servicemix.tutorial.camel</groupId>
      <artifactId>tutorial-camel-su</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
  </dependencies>
  ...
</project>

Cleaning up and doing a first build.

Just do a quick clean-up of the generated pom.xml files (e.g. changing the project names to get more comprehensible logging output) and build the entire project using the command mvn install in the parent project directory. If everything is OK, the output should look like:

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   SMX-Camel :: Tutorial
[INFO]   SMX-Camel :: Tutorial :: Camel SU
[INFO]   SMX-Camel :: Tutorial :: SA
[INFO] ------------------------------------------------------------------------
[INFO] Building SMX-Camel :: Tutorial
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
...
[INFO] ------------------------------------------------------------------------
[INFO] Building SMX-Camel :: Tutorial :: Camel SU
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
...
[INFO] ------------------------------------------------------------------------
[INFO] Building SMX-Camel :: Tutorial :: SA
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
...
[INFO] [install:install]
[INFO] Installing /home/gert/projects/tutorial/tutorial-camel-sa/target/tutorial-camel-sa-1.0-SNAPSHOT.jar
to /home/gert/.m2/repository/org/apache/servicemix/tutorial/camel/tutorial-camel-sa/1.0-SNAPSHOT/tutorial-camel-sa-1.0-SNAPSHOT.zip
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] SMX-Camel :: Tutorial ................................. SUCCESS [5.549s]
[INFO] SMX-Camel :: Tutorial :: Camel SU ..................... SUCCESS [7.849s]
[INFO] SMX-Camel :: Tutorial :: SA ........................... SUCCESS [0.381s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14 seconds
[INFO] Finished at: Fri Feb 15 10:39:06 CET 2008
[INFO] Final Memory: 21M/79M
[INFO] ------------------------------------------------------------------------

Now that we have created the necessary projects, it’s time to really get started with camel

Servicemix Kernel will be started from the cli with:

bin/servicemix

You can deploy web application into it. Servicemix use Jetty as its web container. To deploy you can do inside from osgi shell with:

osgi/install war:file:///your/web/application/archive.war?Webapp-Context=contextname
osgi/start


It will be run in:

http://localhost:8080/contextname

End

And here it is, for your information, my current development stack:

Presentation Layer:

Presentation layer is layer of application which the closest layer to users. Term user here is person, party, or even another machine which asks for and uses service served by application.

Currently, I often faced to different type of developments which is usually only web presentation layer.

• Php – CakePhp (best price and robustness)
• Java – Struts 1.2 (old school fashion)
• Java – JSF (better approach) with JBoss RichFaces

Ajax:

Ajax implementation used to leverage user experience to web application as desktop application as well.

Currently, light weight implementation of ajax used on my development stack, using simple javascript as:

• Javascript – PrototypeJS
• Java – DWR
• Javascript – EXTJS
• Javascript – JQuery

Business Layer:

Business Layer is layer to process business logic of the application.

• Php – CakePhp (its model)
• Java – Spring
• Java – EJB 3

Data Persistence Layer:

Data Persistence Layer is layer to persist data to data source as database.

• Java – JPA with Hibernate
• Java – Hibernate

Project Management Tools:

Project Management Tools consist of wiki, issue-tracking system, and revision control system integrated.

• maven, mainly as build tool
• redmine, rubyonrails-based issue tracker
• trac, python-based issue tracker very easy to use but hard to install

Revision Control System:

Revision Control System is the management of multiple revisions of the same unit of information.

• svn (Subversion)
• cvs, obsolete by svn i think

Unit Test:

Unit test is testing applied to each unit of application

• Java – JUnit

IDE:

Integrated Development Environment mainly as editor, build, and run project.

• Eclipse

Continuous Integration:

CI enable automated build in integration term, so any fallacies in each update can be immediate known.

• Java – Apache Continuum

As java developer, I am familiar with javadoc to write unit documentation of your software, but it’s too technical for user who doesn’t know yet what the aim of the software. User may expect something more descriptive as a serial of essays.

You may know how to write wiki. And the best thing is you can compile serial of essays what I’ve talking about before as group with other coders. Then, if wiki is well-updated, users may find suitable help for them.

But sometimes there are users who in rush and need getting help as quick as possible to start new project. Then you may use, ‘getting started’ as quick start quide to use the software. It would be nice to describe common use-case there, and even nicer if you as coder willing to build small video presentation about it.

All above things will help, but at the end, if users get stuck on something he or she doesn’t know how, they will scream for help. So, there is forum to help, users helping another user.

You may want another addition technologies instead of this list to help reducing learning curve of users. It might help more, and more, and more. Abundant tools to learn, and people needs to learn about it. But someday, maybe we’ll find a day, when people needs to climb learning curve to learn how to learn, as infinitive process.

Basic thought being written as words. Clear type of written thought would be group of sentences called essays. But sometimes thought representation takes form of something unable to describe. Feel, emotion, anger, or even silence of the thought, cannot be described easily. When someone tends to define feeling, somehow we can find the definition won’t be complete and corrupted.

Poets are looking into another approach. They compile feelings into (somewhat of another abstract form) words. You might think, it is useless then.

Ok…

After long journey of this essay, I will invite you to think analogously. Software framework analog to Poetry, and Framework architect as a Poet. And decide yourself who you are.

The question is…?

Are you sensible person who has state of arts? or just a simple-minded who talking to much but avoid the essence…