Richard has summarized my potential responses :) Here the reason why: My aim is to have 2 web application in the same OSGI container (1 OSGI container consumes less memory than 2 OSGI container). The first application is dedicated to public http requests, and the second application is dedicated to admin http requests (on a different network card). By using 2 different network port for each web application, I'm able to inject firewall rules to authorize requests for the first web application from everywhere, and to restrict the access to the second web application for admin request only.
I will play with Pax Web. Thanks for your responses! -----Message d'origine----- De : Charles Moulliard [mailto:[email protected]] Envoyé : lundi 1 février 2010 17:39 À : [email protected] Objet : Re: Is there a way to start 2 Http service on 2 different port? So. Let's wait Loic feedback ;-) 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 2010/2/1 Richard S. Hall <[email protected]> > On 2/1/10 11:19, Charles Moulliard wrote: > >> Loic, >> >> There is an alternative to Apache Felix HTTP Service. You can use PAX Web >> osgi bundles to configure one or several jetty instances. Here is the doc >> : >> >> http://wiki.ops4j.org/display/paxweb/Advanced+Jetty+Configuration >> >> but What would you like to do with two separate HTTP instances (using a >> different port number) on your OSGI server ? >> > > That, I don't know. I was just responding to what I interpreted the > original question to mean. :-) > > -> richard > > > Even if you run two separate >> instances of your HTTP service on Felix, programmation will be required to >> attach servlets/jsp pages, ... and so on to one instance instead of the >> other. >> >> 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 Mon, Feb 1, 2010 at 5:02 PM, Richard S. Hall<[email protected] >> >wrote: >> >> >> >>> On 2/1/10 10:15, Charles Moulliard wrote: >>> >>> >>> >>>> Hi Loďc, >>>> >>>> >>>> You can change the port number. It is explained here : >>>> >>>> http://felix.apache.org/site/apache-felix-http-service.html >>>> >>>> Section : >>>> >>>> Configuration Properties >>>> >>>> The service can both be configured using OSGi environment properties and >>>> using Configuration Admin. The service PID for this service is >>>> "org.apache.felix.http". If you use both methods, Configuration Admin >>>> takes >>>> precedence. The following properties can be used (some legacy property >>>> names >>>> still exist but are not documented here on purpose): >>>> >>>> - org.osgi.service.http.port - The port used for servlets and >>>> resources >>>> available via HTTP. The default is 80. >>>> - org.osgi.service.http.port.secure - The port used for servlets and >>>> resources available via HTTPS. The default is 443. >>>> >>>> >>>> >>>> >>> That changes the port, but how precisely to you get two differently >>> configured services? You cannot configure the same PID twice for two >>> different services, right? >>> >>> I am not a user of the HTTP Service (or Config Admin for that matter), >>> but >>> unless there is some sort of managed service factory involved, there will >>> only be one instance of the service, correct? >>> >>> -> richard >>> >>> 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 Mon, Feb 1, 2010 at 4:11 PM, Loďc Cotonea<[email protected]> >>>> wrote: >>>> >>>> >>>> >>>> >>>> >>>>> Hi everybody, >>>>> >>>>> >>>>> >>>>> My web application is using an http service that listen on a network >>>>> port. >>>>> This port is reserved to frontend communication. However, I would know >>>>> if >>>>> there is a way to open a second http service on another network port to >>>>> serve some backend http requests? >>>>> >>>>> >>>>> >>>>> Thanks >>>>> >>>>> >>>>> >>>>> Loďc >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >>> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
