ServiceMix is fully jbi compliant. You can limit yourself to the JBI specification, but ServiceMix can go a bit further.
As for the tutorial, it produces JBI compliant artifacts, but that's true we use a maven plugin to ease the work of the user: feel free to not use it if you prefer, but it' s just a tool used to create the jbi descriptors and package the SUs and SAs as required by the JBI specification. For the deployment method, you can also use the standard JBI depoyment method which use ant tasks, but again, we offer a simplier way to deploy JBI artifacts either using the maven plugin or by copying the artifact in the hotdeploy folder. So this is really about tooling. Other JBI ESBs may provide other kind of tools, but these are just tools which has nothing to do with the specifications per se. And AFAIK, JbossESB does not support JBI .... On Sun, Jun 8, 2008 at 12:48 AM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Hi all, > > Based on the various explanations of JBI that I have tried to understand, I > have been led to believe that JBI is an attempt to bring some kind of > standardisation to the world of business messaging systems. > > However while evaluating both ServiceMix and JBossESB, I am struggling to > see any evidence of any kind of standards anywhere. > > ServiceMix describes a basic tutorial on how one might get started here: > http://servicemix.apache.org/21-beginner-starting-the-maven-project.html. > The trouble is everything in the tutorial revolves around a ServiceMix > specific maven plugin, creating ServiceMix archives of some kind (the > tutorial isn't clear on exactly what the artifacts are it is producing), and > eventually using a ServiceMix specific method to deploy the artifacts to the > ServiceMix container. > > In the case of JBossESB, a JBoss specific ESB plugin was created by > somebody, and there is talk of an "esb" archive (a glorified zip file). The > structure of this file contains a non standard file called jboss-esb.xml, > and therefore by definition, this file is no longer container agnostic or > standards compliant. > > So, is ESB just EJB2 all over again, where each container vendor "embraced > and extended" the standard to create their own incompatible systems? > > Regards, > Graham > -- > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
