Hi Ryan,
This is probably a good question to ask users_at_open-esb.dev.java.net
(or even the 'dev' alias).
My take on this would be that the app server becomes just one of many
service engines which can expose a legacy system via JCA while a JBI
binding component (BC) plugs right into the ESB and NMR. A BC is
exposed using WSDL. There is also some install and management
dimension to JBI vs. JCA.
The OpenESB wiki is also a good place to look:
http://wiki.open-esb.java.net/
On writing JBI components:
https://open-esb.dev.java.net/nonav/public/jbi-comp-examples/Developing_JBI_Components.html
cheers,
-Alexis
On Jun 11, 2008, at 6:03, Ryan de Laplante wrote:
> A while back I wrote a JCA connector to communicate over sockets
> using a proprietary protocol to an EIS. Is OpenESB JBI an
> alternative to JCA connectors? Why would I choose to use JBI over
> JCA? Can someone point me to some pages explaining how to create a
> JBI component?
>
>
> Thanks,
> Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>