THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Warning | ||
|---|---|---|
| ||
The items listed on this wiki page is just ideas for the roadmap. Anything is subject for change. When development of Camel 3.0 starts we will update status here which items have been implemented in the source code, and which have been discarded/deferred etc. | ||
| Info | See Camel 2.7 | See Camel 2.7 |
See the Camel 2.7 - Roadmap as we have decided to bring forward some of the goals and introduce them earlier in the Camel 2.7 release. |
JDK 1.6+
Camel 3.0 should bump the JDK minimum version to 1.6.
Camel 1.x/2.x supports JDK 1.5+.
Spring 3.x
Camel 3.0 should bump the minimum version of Spring to 3.0+.
Camel 1.x/2.x supports Spring 2.0+
Clearer Architecture of Camel Core
...
@deprecated features, methods, etc. is to be removed.
Logging
We should switch from commons-logging to slf4j
Stream caching
We could add support for using HawtDB as the persistent store for streams which overflow to disk store.
...
See above about less Spring dependency.
Refactor UnitOfWork
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