On 23 July 2013 20:13, wcpolicarpio <walter.policar...@morgansolar.com> wrote: > Hi James, > > That would be awesome! I will definitely anticipate your new cartridge.
Cool, I'll reply to this thread when I've got a blog on how to get started. > I saw the hawt.io interface and it looks cool. Thanks! > (http://macstrac.blogspot.co.uk/2013/06/introducing-apache-camel-based-open.html). > > I have a follow-up question. Is it possible to deploy the camel route in a > jboss/tomcat gear and communicate to another gear(e.g. php with a mysql)? Yes. On OpenShift each 'gear' is a separate virtual computer (or unix lightweight container - LxC) on some hardware somewhere. An 'application' is zero to many gears (depending on auto-scaling or manual-scaling). The easiest way to communicate between gears is to use HTTP; since each application gets its own domain name (which abstracts the auto-scaling & HTTP load balancing underneath), so any gear/app can talk to any other gear/app via https://appname-username.rhcloud.com/ for example if using OpenShift Online. In Camel terms there are a few different endpoints which under the covers use HTTP (e.g. http, http4, netty-http, jetty, cxf, restlet etc) http://camel.apache.org/components.html For non-HTTP communication (e.g. messaging), we're working on nicer ways to perform inter-gear communication in the Fuse cartridge & with the OpenShift team... -- James ------- Red Hat Email: jstra...@redhat.com Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration
