It might be doable. I guess the way to do that would be to define the JBI endpoint as a wrapper to a camel endpoint. When the JBI endpoint would be initialized / started, a camel route would be created for it. Not sure how well camel endpoints can handle the JBI lifecycle where new requests are not accepted, but existing exchanges are still processed until completion (for a consumer endpoint).
On Mon, Feb 2, 2009 at 17:53, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > Let's include the camel folks in this discussion. > > > On Feb 2, 2009, at 11:51 AM, Hadrian Zbarcea wrote: > >> Hi, >> >> Another option is to implement such components in Apache Camel and provide >> a way to easily wrap a camel component in a jbi component. Such components >> are useful to users who only use Camel too, and it would be a pity to >> duplicate the work. >> >> Thoughts? >> Hadrian >> >> >> On Feb 1, 2009, at 2:28 AM, Jean-Baptiste Onofré wrote: >> >>> Hi Chris, >>> >>> Thanks. >>> >>> I propose the following priority for BCs : >>> - servicemix-ldap >>> - servicemix-exec >>> - servicemix-jdbc >>> - servicemix-asterisk >>> - servicemix-talend >>> - servicemix-sap >>> - servicemix-cics >>> >>> What about the servicemix-ejb, does it make sense or do we consider that >>> CXF-SE is enough ? >>> >>> Regards >>> JB >>> >>> On Saturday 31 January 2009 - 17:00, Chris Custine wrote: >>>> >>>> Hi JB, >>>> A while back I did some playing with asterisk-java ( >>>> http://asterisk-java.org/) in SMX4 and OSGi so I would be happy to help >>>> create a more general purpose JBI component. My code never evolved >>>> beyond >>>> sandbox quality, but I will dust it off and maybe soon we can chat about >>>> some features. >>>> >>>> Chris >>>> >>>> -- >>>> Chris Custine >>>> My Blog :: http://blog.organicelement.com >>>> Apache ServiceMix :: http://servicemix.apache.org >>>> Apache Directory Server :: http://directory.apache.org >>>> >>>> >>>> On Fri, Jan 30, 2009 at 1:27 PM, Jean-Baptiste Onofré >>>> <j...@nanthrax.net>wrote: >>>> >>>>> Dear all, >>>>> >>>>> I'm completing the unit tests on the SMPP BC but it's now quite the end >>>>> (Lars has already included on the svn repo) (it's the SM-1623). >>>>> I have begun to work on the SM-1771 (extend the SU <classpath/> >>>>> location >>>>> support). >>>>> >>>>> But, I would like to implement new components : >>>>> - JDBC BC : read and write messages from JDBC >>>>> - Talend BC : read and write messages from the Talend ETL >>>>> - Asterisk BC : read and write from Asterisk VoIP software >>>>> - Exec BC : read and write from command execution (using commons-exec) >>>>> - LDAP BC : read and write from LDAP (using JNDI) >>>>> - CICS BC : read and write messages from CICS mainframe >>>>> - SAP BC : read and write messages from SAP >>>>> - EJB BC : currently, I use CXF-SE to call an EJB. Maybe a component >>>>> exposing directly (either if it use CXF-SE in background). >>>>> >>>>> What do you think about these components ? >>>>> Does it make sense (for me, it's the case as I have request from >>>>> customers >>>>> to support in FSB/SMX legacy platform such as CICS, SAP, JDBC, etc) ? >>>>> >>>>> I'm ready to begin this work if you are OK. >>>>> >>>>> Regards >>>>> JB >>>>> -- >>>>> Jean-Baptiste Onofré (Nanthrax) >>>>> BuildProcess/AutoDeploy Project Leader >>>>> http://buildprocess.sourceforge.net >>>>> j...@nanthrax.net >>>>> PGP : 17D4F086 >>>>> >>> >>> -- >>> Jean-Baptiste Onofré (Nanthrax) >>> BuildProcess/AutoDeploy Project Leader >>> http://buildprocess.sourceforge.net >>> j...@nanthrax.net >>> PGP : 17D4F086 >> > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
