Thanks! I gave it a quick skim and think this looks very interesting.
The original implementation of my connector ran on JBoss and used their
proprietary JMX Service features where I could take advantage of
stop/start events etc. Other than being told when to stop/start, it was
in full control of itself.
When I ported it to JCA, it couldn't run like a background program
responding to events from the server etc. It became one of many
connections in a pool that are flushed and re-created etc. The source
became very large and complex, difficult to read, etc. For example, a
request is now called a "Record". I had to create a separate project
to expose the features as a web service.
I think JBI looks more appropriate for our application. I will
consider changing over sometime in the future. I like that JBI is a
standard, so I won't be tied to GlassFish if we have issues.
I'm wondering if I can build my JBI component as a Maven2 poject? Not
all developers of our next app will be using NetBeans.
Thanks,
Ryan
Alexis Moussine-Pouchkine wrote:
> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>