-
1. Re: Gateway or Service Component we've not tried yet or actually don't have
kcbabo Apr 11, 2012 8:04 PM (in response to igarashitm)Thanks, Tomo. I have edited your gateway table a bit and added some comments:
JBoss ESB SwitchYard Comments JCA JCA Gateway Component Support for both inflow and outbound SQL Camel Gateway : SQL Need to confirm all JBoss ESB options exist in
Camel SQL Component.
FTP, FTP/S Camel Gateway : FTP Review required of FTP/S support in Camel FTP
component.
HTTP, HTTP/S ??? Need to investigate if/how we could use existing HTTP
and HTTP/S listeners in AS7.
UDP Camel Gateway : Netty Verify that udp options in JBoss ESB are available
in Camel Netty component.
TCP Camel Gateway : Netty Verify that tcp options in JBoss ESB are available
in Camel Netty component.
JBoss Remoting ??? Not sure we need this. Schedule Camel Gateway : Quartz Verify that schedule options in JBoss ESB are available
in Camel Quartz component.
Hibernate ??? Not sure we need this. File Camel Gateway : File Verify that file options in JBoss ESB are available in Camel File component.
JMS Camel Gateway : JMS Biggest problem here is figuring out which options are
supported.
For all instances where we use a Camel gateway, we need to make sure there is an associated configuration schema which contains the configuration values we will support for that gateway.
-
2. Re: Gateway or Service Component we've not tried yet or actually don't have
splatch Apr 11, 2012 5:49 AM (in response to kcbabo)Hey,
For TCP and UDP protocols I think we can stay with Netty (and camel-netty). There is lots of changes going to be introduced in Camel 2.10 within mina component (especially switch to mina 2.x to support async callbacks).
It's also worth to note that camel handles differently HTTP calls and Web Service invocations - eg. uses different URI scheme to invoke external SOAP endpoint or simple servlet.
-
3. Re: Gateway or Service Component we've not tried yet or actually don't have
kcbabo Apr 11, 2012 8:07 PM (in response to splatch)Sure thing. I updated the table to reflect the use of camel-netty. For all of the options using a Camel component we need to x-ref with our existing installation to make sure currently supported options are available. Documentation is probably the best place to start.
Also, we still need to figure out the HTTP approach. There are a lot of good reasons to reuse the existing HTTP listener in AS7 if possible.