THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- New async routing leveraging the JDK concurrent API to replace AsyncProcessor DONE
- default to using transacted mode along with transacted error handlers CAMEL-866 DONE
- improve smart completion of Java & XML DSLs DONE
- make more endpoints easily configurable as beans in Spring XML CAMEL-506 DONE
- improve the DSL
- get rid of
consumer.options for common options DONE - support # notation for URI options to lookup a reference in the bean registry DONE
- consider how we can expose some of the ExpressionBuilder we have in Javs DSL in the XML DSL as well DONE
- get rid of
- solving MEP issues DONE
- using Camel${component}${name} pattern as header keys instead of using package names with dots that isn't likely to be transported by JMS or other transport types DONE
- OSGi sample and wiki documentation DONE
- Add the OSGi integration test support DONE
- All of the bootstrap mechanisms (components, endpoints, converters, registry) should be osgi aware DONE
- ServiceMix and Camel sample and wiki documentation DONE
- Easier transacted route configuration DONE
- onComplete(), onFailure() callbacks to UnitOfWork on a Exchange allowing custom code being executed when a Exchange completes DONE
- Get the onComplete, onFailure callbacks on UnitOfWork exposes in the DSL and used by component to do cleanup after processing an exchange IN PROGRESS DONE
Refactoring of code and internal API changes
...
Camel 2.1 Design
Main features
- More JMX stuffOverhaul of JMX and much improved JMX monitoring and management
- More advanced and easier thread pool configuration such as from managed environments
- setting core pool size as number of processors + 1
- global, group, local configuration groups for thread pool configurations
Internal
- reduce the need to copy exchanges CAMEL-872
- interceptors should be runtime applied and not woven in at design time - separate design time vs. runtime stuff
Internal
- reduce the need to copy exchanges CAMEL-872
OSGi
- Much improved OSGi (willem)
- Making component/converter discovery use OSGi services when in an OSGi environment
- Making ObjectHelper.loadClass aware of OSGi environment
- More documentation and samples
...
- have nice Spring 2 namespace schemas for different endpoints for nicer IDE completion
- pluggable DSL (Hadrian) (Groovy will be able to do this)
- component loading being isolated and better error reporting if failed to load
- better annotation based type converter loading