Hi, Here is a list of features that I think could be interesting to implement in future versions of SMX Kernel :
- Improve JNDI support and integration with JTA transaction management (to have one Transaction manager by SMX server allowing to handle activemq transactions + hibernate transactions ...), - Add EJB3 support, - Generate separate logs for bundles or features, - Provide web admin interface, - Clustering of SMX (based why not Camel on loadbalancing, integration with terracota, ...), - Propose architecture master/slave to deploy application from one server to several SMX4 slaves, - Improve feature to allow refresh or re installation of bundles, - Integration with Eclipse to debug/deploy/undeploy application, - Provide maven plugin to deploy/undeploy/stop/start bundles or project (= list of features = list of bundles) - For the administrator or profiler we need profiling to detect where we have memory issues/gaps, ... - Backup strategy, - Rotation of the file logs (defined through etc config file or web administration console) - JMX support - Alerting support in case or problem with bundles (active --> inactive) Regards, ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://www.nabble.com/Proposition-for-new-features-about-SMX4-Kernel-tp22843141p22843141.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
