Page History

...

• Using out of the box functionality (http component, jsr181 comp, eip comp,...) to create an own SA
• List Maven archetypes and when to use which
• List all available components and give some information about them (type, purpose, usage in any example,...)
• undeployment, see http://mail-archives.apache.org/mod_mbox/geronimo-servicemix-dev/200610.mbox/%3cb23ecedc0610011247v7b435be0ka00ee8e8375230e9@mail.gmail.com%3e
• a central debugging page listing the possibilities and linking to the appropriate pages/sections.
  • run SMix from source in Eclipse in debug mode
  • (permanent) increase the log level to debug in %SERVICEMIX_HOME%\conf\log4j.xml (by changing everything from "info" to "debug") or (temporarily) using JConsole and watch the log file
  • Eclipse WTP server start in debug mode
  • remote debugging of the JVM (default port 5005, can be altered in servicemix.bat in line set DEFAULT_JAVA_DEBUG_OPTS=) by first calling set SERVICEMIX_DEGUG=true then servicemix.bat
  • component debugging in eclipse, see 2nd comment at http://fiveclouds.blogspot.com/2006/01/spent-one-of-those-days-waiting-for.html^{Image Added}
  • your idea
• short text telling what SMix is better suited for than the competitors (mule, celtix, webshpere,...). Maybe in form of use cases? Or in terms of missing features, performance, price, ...?