| Target release | Release name or number |
|---|---|
| Theme | Roadmap focus area |
| Document status | |
| Document owner | |
| Designer | Lead designer |
| Developers | Lead developer |
| QA | Lead tester |
|
Implementing Enterprise Integration Patterns using OpenESB is currently done using only BPEL SE. BPEL SE is considered heavy and has performance impact for simple EIP patterns like routing, mediation, etc. We need to have a simpler and lighter way of implementing EIPs. We considered Apache Camel can serve the purpose and it is widely used. By utilizing apache camel support in OpenESB we will be able to utilize the benefits from both the worlds.
| # | User Story Title | User Story Description | Priority | Notes |
|---|---|---|---|---|
| 1 | Ability to run camel applications on OpenESB without using JBI endpoints | Describe the user and what they are trying to achieve | Must Have |
|
| 2 | Receive messages from JBI endpoint to camel | |||
| 3 | Send messages from camel to JBI endpoints | |||
| 4 | Send reply messages to JBI endpoints | |||
| 5 | Receive reply messages from JBI endpoints | |||
| 6 | Support for other DSLs than Java DSL? | |||
| 7 | Ability to add external libraries after service engine installation | |||
| 8 | Wizard for developing InOut Camel endpoints | Currently the wizard supports InOnly endpoints | ||
| 9 | UI support or desining camel routing. | Can we utilize any existing netbeans camel modules for this? |
Include any mockups, diagrams or visual designs relating to these requirements.
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |