Hi, Yes, this need is one of the requirements [1] for the update: The Http Service will be required to expose service registration properties indicating the interface (local IP address) and port on which the service is active for HTTP and HTTPS.
The Http Service is basically just concerned about serving HTTP (and HTTPS) requests through Servlets (and providing static resources). So except for the HTTP and HTTPS information nothing else can be required from the Http Service. But any concrete implementation is free to expose whatever properties they like. So a tomcat based implementation may well expose the AJP13 port. Hope this helps. Regards Felix [1] https://www.osgi.org/bugzilla/attachment.cgi?id=35 Am 25.10.2012 um 09:02 schrieb Balázs Zsoldos: > Hi, > > I see that there is a discussion about the enhancement of the HttpService. I > would like to share some thoughts that we faced with before: > > Jetty and Gemini Web (Tomcat) has an amazingly similar interface defined to > query the opened ports with protocols. To use them in our integration test > mechanism we had to write a class that hides the jetty/tomcat specific > functions and makes it possible to query the opened ports in a common way. > Why is it necessary? It is because in case of jetty we define port 0 > (randomly assigned port) to be sure that it will use a free port on our CI > server. However, this could be very useful in other cases as well. > > Please think of having a simple interface (like ServletContainer or > HttpServer) defined to query a Map of opened port-protocol pairs with some > pre-defined constant values for protocol types (like HTTP, HTTPS, AJP13). > > Thanks and regards, > Balazs Zsoldos > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
