Hi Loic, An alternative could be that you use Apache Camel framework. This routing and mediation framework (http://camel.apache.org/) has implemented Enterprise Integration Patterns ( http://camel.apache.org/enterprise-integration-patterns.html) and propose additional like loadbalancing. With the pattern loadbalancing, you can create several HTTP endpoints because this instance create a new Jetty instance. In this case, you can define the port number + server ip address.
You can find more info here : http://camel.apache.org/jetty.html I have created a small project for ServiceMix 4 platform (wich is an OSGI container running Felix or Equinox through Apache Felix Karaf). : https://issues.apache.org/activemq/browse/SMX4-454 Kind regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard Linkedlin : http://www.linkedin.com/in/charlesmoulliard Apache Camel Group : http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm On Tue, Feb 2, 2010 at 8:26 AM, Cotonéa Loic <[email protected]> wrote: > You're right. However some port forwarding firewall rules can be a work > around to the ip binding problem. > > For the moment, I think that I will simply use 2 Osgi container: one for > the > frontend web application, and another one for the backend web application. > > Le 2 févr. 2010 06:55, "Rob Walker" <[email protected]> a écrit : > > If I understand you correctly, as well as the problem of different ports, > and Richard's point on how to tell which HttpService to register aliases > with (which could be worked around by convention that the HttpService > publishes it's port as a service property - something I think we mod'd the > original Felix jetty based service to do. > > But I think you have a bigger problem: > > > > (on a different network card) > To achieve that you will also need each HttpService bind it's listener > socket to just the local IP address for that 1 network card - which means > your config will also need to specify a local IP address to bind the > listener too as well as the port. Most HttpService implementations probably > assume the listen will go to all network interfaces. > > - Rob > > > > Loïc Cotonea wrote: > > > > Richard has summarized my potential responses :) > > > > Here the reason why: > ... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-... >
