Page History

...

Instead of having both uri and ref for endpoints, we should unify this and only use uri. If people want to use ref, then they can do that using "ref:xx" as an uri. This would simplify code as we dont have to check for either one.

Less Spring dependencies

DONE in Camel 2.9

In camel-core we use the Spring JMX annotations to more easily enlist our MBeans. We should move that logic to camel-spring. And introduce a Camel specific annotations to replace those. For example ActiveMQ does that. This allows us to use camel-core with JMX without any spring JARs at all. End users can still use the Spring JMX annotations in their custom code / components. They just need camel-spring on the classpath.

...

Introduce Camel JMX annotations

DONE in Camel 2.9

See above about less Spring dependency.

...

The implementation of DefaultUnitOfWork seems to have transformed itself into a to broad concern where unit of work is doing a bit more work than the transactional aspect that ties to its name.
Maybe this implementation should be named ExchangeContext and we can introduce a simpler UnitOfWork concept. This would also allow us to refactor the SubUnitOfWork into a general parent/child unit of work concept.
However this requires API changes and thus is best kept for Camel 3.0

Improvements to ThreadPoolProfile for thread management

We could move ThreadPoolProfile from org.apache.camel.spi to org.apache.camel and have it in the root package.
We could introduce a ThreadPoolProfileBuilder for support builder style creation of profiles.
The API for ExecutorServiceManagement could add support for creating new thread pools based on a profile. Then people can use the builder style to set the settings they want for the thread pool, and have the ExecutorServiceManagement create the thread pool.