I'm seeing lots of noise about JSR-208/Java Business Integration (JBI) out of this year's JavaOne.
As a layperson, JBI looks to me like yet another container/component model to add to the EJB/Spring/Pico family.
Naturally, JBI defines a new set of lifecycle, context, deployment and configuration details, but the basic "message comes in, container loads code, code sees message" machinery we all know and love from ASP.NET/Servlets/CORBA/DCOM/ISAPI/httpd is there in all its glory.
What I don't understand is how a JBI container all that different from an EJB container, and if not, why does the world need both? Moreover, when would someone write a JBI service engine vs. writing a JAX-WS component? Also, why didn't IBM and BEA embrace this thing last fall?
Hopefully, the Java cognoscenti will educate me…
Posted
Jul 01 2005, 10:15 PM
by
don-box