[CONF] Apache ServiceMix > Roadmap

[confluence]

Roadmap Page edited by Jean-Baptiste Onofré Changes (5) ... ** ActiveMQ 6 ** (not sure if CXF is planning a CXF 3) * Optional JBI support and ServiceMix Components * NMR improvements * Renaming of the NMR (ServiceMix GL for Gateway Layer ?) and improvements: ** Service Registry/Custom Registry: define an agile architecture to let usage of custom service registry in the GL. The users can define their own service registry, business oriented. ServiceMix GL could provide an API (as the Event or Messaging one) to interact between Service Registries and Endpoints/Messaging. ** Service Locator: the purpose is to be able to delegate a service lookup to another ServiceMix GL instance. It's not clustering, it's more farming. It means that there is no state replication between ServiceMix instance, only service delegation. ** Distributed Transaction: all components integrated in ServiceMix (CXF, Camel, ActiveMQ, ...) should share the same transaction manager. The transaction manager should be highly configurable to be able to use a remote one (provided by a JEE application server or a pure transaction manager such as Tuxedo, etc). ** New clustering/clouding support, allowing a clustering mechanism including state replication and cluster manager. * BPM Layer ** Better and deeper integration of Apache ODE WS-BPEL engine ** Core support of a rule engine (Drools ?) ** Support of a BPM N2 component (Activiti ?) ** Plugin architecture to allow plug and play of BPM component (Bonita, Agila, jBPM, ...) * Tooling improvements: ** New karaf shell commands ** WebConsole for monitoring and administration Full Content Upcoming releases roadmap ServiceMix 4.4.0 Upgrade of major dependencies: Latest Karaf 2.2.x Camel 2.7 Latest CXF 2.3.x Latest ActiveMQ 5.x Build maintainability Upgrade to JDK 1.6 and Maven 3 POMs Features descriptors Documentation For a full list of issues for the ServiceMix 4.4.0 release, have a look at https://issues.apache.org/jira/browse/SMX4/fixforversion/12315742 ServiceMix 5.0.0 Upgrade to next major versions Karaf 3 Camel 3 ActiveMQ 6 (not sure if CXF is planning a CXF 3) Optional JBI support and ServiceMix Components Renaming of the NMR (ServiceMix GL for Gateway Layer ?) and improvements: Service Registry/Custom Registry: define an agile architecture to let usage of custom service registry in the GL. The users can define their own service registry, business oriented. ServiceMix GL could provide an API (as the Event or Messaging one) to interact between Service Registries and Endpoints/Messaging. Service Locator: the purpose is to be able to delegate a service lookup to another ServiceMix GL instance. It's not clustering, it's more farming. It means that there is no state replication between ServiceMix instance, only service delegation. Distributed Transaction: all components integrated in ServiceMix (CXF, Camel, ActiveMQ, ...) should share the same transaction manager. The transaction manager should be highly configurable to be able to use a remote one (provided by a JEE application server or a pure transaction manager such as Tuxedo, etc). New clustering/clouding support, allowing a clustering mechanism including state replication and cluster manager. BPM Layer Better and deeper integration of Apache ODE WS-BPEL engine Core support of a rule engine (Drools ?) Support of a BPM N2 component (Activiti ?) Plugin architecture to allow plug and play of BPM component (Bonita, Agila, jBPM, ...) Tooling improvements: New karaf shell commands WebConsole for monitoring and administration Change Notification Preferences View Online | View Changes | Add Comment