Hmm, briefly looking into this - i'm wondering if you see any conflicts sharing the same web container with other EE applications? I.e. are there any configuration parameters defined in the OSGI spec - like vhosts, ports or context-root?
The general recommended configuration mechanism is ConfigurationAdmin. The HttpService spec specifies two Framework properties for the Http ports, which are unrelated to ConfigurationAdmin. In AS7 that port configuration should come from the http-binding and be visible to management agents that work on top of ConfigAdmin and Framework properties.
The following OSGi environment properties are used to specify default
- org.osgi.service.http.port – This property specifies the port used for servlets and resources accessible via HTTP. The default value for this property is 80
- org.osgi.service.http.port.secure – This property specifies the port used for servlets and resources accessible via HTTPS. The default value for this property is 443
I'm currently working on a general AS7 Configuration Service that can be used to store arbitrary configuration data for services and deployments. The OSGi ConfigurationAdmin would access that common data store.
For your work, it should be sufficient to build on what is there already (i.e. the http-binding) There is thing called osgi-http-binding, which can be removed once we have an HttpService implementation on top of a well defined JBossWeb API.
It looks like currently (which is 7.1.1 for me) there is a Jetty WebServer started when I enable the OSGI HTTP Service. Is there a way to map this to the JBossWeb container so I dont need to configure two different servers? Specifically I am interested in running the felix web console, which has that dependency to the OSGI http service.