-
1. Re: Jetty endpoint exposed on port 80, not 8181
ffang Jul 23, 2013 8:14 PM (in response to ksimpson)You use
from("jetty:http://remoteVMName/foo/FooService")
here, which means a standalone jetty server port, but not the http-osgi sevice(8181), and the default port for
jetty:http://remoteVMName/foo/FooService
is 80, as you didn't specify the port in URL
Freeman
-
2. Re: Jetty endpoint exposed on port 80, not 8181
ksimpson Jul 24, 2013 11:16 AM (in response to ffang)This is running in JBoss Fuse on RHEL6... When run on Windows JBFuse, the service/route is available on port 8181; not sure I've ever tried to connect to port 80 when JBFuse is running on Windows... simply never occurred to me.
From your answer, am I to infer that JBFuse has a standalone Jetty server in addition to the Camel Jetty component? And/or that by not specifying a port explicitly, Jetty defaults to its standard port and ignores the configuration in etc/system.properties?
UPDATE: After deploying again on Windows without port specified, it connects on port 80 as you described. I think some of the example Camel routes I've seen used 8181, must of gotten stuck in my head... Thanks Freeman!