Here is my list: 1. Improve the Maven 2 jbi plugin. Make sure it works flawlessly when deploying components. I.e. no problems shutting down shared libs/components etc. When it works development goes very smoothly. I figure the faster developers can work problem free the quicker Smix will improve.
2. Eclipse plugin - project generation, control of Smix during development, graphical creation/configuration of endpoints w/ automatic generation of XBean and java files. How nice would it be to do 50%+ of your work creating a SA by using a tool which allows one to drop in components and hook them together. 3. The EIP component is a great start, but the book 'Enterprise Integration Patterns' presents so much more. Let's get those other patterns into the component, or in a new one. This would probably have a large impact on usability out of the box. If all the good plumbing stuff comes in the distribution then end users main problems becomes creating, finding and using bc's to integrate in their legacy systems (and stuff :). 4. In depth description of Servicemix = better documentation. Would be nice to see an archetectural break down with corolations to JBI. The flow of documentation is too broken up. Maybe the community could put together a 'table of contents' which would better prepare the reader as they linearly progress through the documentation. Then we could merge in all the current documentation to fit the toc. A problem I have had is having to jump all around the documentation to find references. This eats up lots of time. If the documentation better prepared you during the initial reading for what comes later, then the problem could be lessened. 5. Maybe a subproject that involves creating integration adapters (BC's?) that can be posted by users so that others can share them, rather than reinventing the wheel. -- View this message in context: http://www.nabble.com/User-Feedback-Request-tf2356023.html#a6574533 Sent from the ServiceMix - User mailing list archive at Nabble.com.
