Page tree
Skip to end of metadata
Go to start of metadata
March 2011
Friday March 17, 2011

FUSE ESB Training - Apache Camel

Thursday March 17, 2011

FUSE ESB Training - Apache ServiceMix

Wednesday March 2, 2011
  1. Downloaded Fuse ESB 4.3.1
  2. Reading (
  3. Reading (
    1. Built all examples with Maven 3.0 (Although only v2.2.1 is officially supported)
      1. Ran the prebuilt CXF-JAXRS example.
        1. Modified, built, deployed and ran the CXF-JAXRS example. (built with both Eclipse Helios and Maven from Windows command shell)
        2. Used both the web console and shell to start and stop the CXF-JAXRS example.
      2. Deploying a Web Service into Fuse ESB
Previous Work Performed by Steve Masover


Here's what I did in March of last year ... might be worthwhile looking for newer versions of everything as this was a long time ago (I didn't realize just how long....). Apologies for the wiki markup, it was the cleanest way to extract the embedded links....

  1. Installed FUSE on 4 Mar 2010. 4.2.0 was available, but initial payment service example was built on, therefore ...
  2. Built and ran example per Getting Started documentation. This was run using a locally installed instance of mvn (v2.2.1, run using JDK 1.6.0_18)
  3. Built in Eclipse v3.5 and m2eclipse plugin (with some fiddling re: JSR181 dependency, replacing a specified and apparently unavailable BEA jar with an xfire jar) – installed as FUSE osgi bundle, but failed to resolve dependencies for or start – the payment-service-se service described in an ESB webinar downloaded from the FUSE Open Source SOA Webinars page.
    1. dependency resolution failures were variants on the following: smx@root:/> osgi/start 178
      ERROR CommandLineExecutionFailed: org.apache.geronimo.gshell.command.CommandException: org.osgi.framework.BundleException: Unresolved constraint in bundle 178: package; &(package=org.springframework.beans.factory.config)(version>=3.0.0))
    2. attempted multiple fixes to address this problem, including specifying spring dependencies explicitly in POM; manually installing spring JARs as OSGi bundles (probably missed a concept or two here); etc. – to no positive effect
    3. this error seems to point to a dependency in the Getting Started example also; have not fully analyzed POM differences, etc. that might explain different results
    4. the upside of banging against these errors was an exploration of the ServiceMix command line interface; cf. documentation


  • No labels