Standards are important. However, history has shown that standards/specifications come and go, whereas requirements persist. So, for example, in the case of transactions, we've had XA, OTS, TIP, BTP, WS-CAF, WS-TX, JTA, but at their core they are doing the same thing. Messaging is another good example: CORBA messaging, JMS, WS-RX, etc. Hence the reason that our first target will be to produce a core ESB framework that matches requirements and ignores specifications in this area: we want something that will last and won't require re-implementation several years from now.
At present JBossESB uses components that adhere to the following standards:
- Web Services, including support for SOAP 1.1 and 1.2.
- JEE, including support for JMS, JTA and EJB3.
- HTTP, FTP.
It should be noted that the above mentioned standards are not mandated by JBossESB, e.g., it is entirely possible to deploy an application on JBossESB that does not use or require Web Services.
In terms of future standards support, the following ESB/SOA standards are on our roadmap:
- JBI: the community may provide a bridge for JBI 1.0. The next version of the standard, JBI 2.0 is evolving slowly and we intend to support it if there is sufficient need.
- SCA: we have publicly announced our intention to support SCA and work with IBM and others within the Tuscany project.