[
https://issues.apache.org/jira/browse/FELIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762373#action_12762373
]
Sten Roger Sandvik edited comment on FELIX-1704 at 10/5/09 2:08 PM:
--------------------------------------------------------------------
Yes, it should reflect the confguration properties. I do not know why it's
configured. Let's just reflect the configuration properties for now if no one
has any good reasons for doing otherwise. So, should we use:
org.osgi.service.http.port
org.osgi.service.http.port.secure
Or?
org.apache.felix.http.port
org.apache.felix.http.port.secure
was (Author: srs):
Yes, it should reflect the confguration properties. I do not know why it's
configured. Let's just reflect the configuration properties for now if no one
has any good reasons for doing otherwise. So, the port properties should then
be: org.osgi.service.http.port, org.osgi.service.http.port.secure.
> Support for port as service properties
> --------------------------------------
>
> Key: FELIX-1704
> URL: https://issues.apache.org/jira/browse/FELIX-1704
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Affects Versions: http-2.0.2
> Reporter: Sten Roger Sandvik
> Assignee: Sten Roger Sandvik
> Fix For: http-2.0.4
>
>
> Support assigned port in Jetty as service property. Both secure and non
> secure. Use the same logic as in old Jetty http service 1.0.1.
> * org.apache.felix.http.svcprop.port
> * org.apache.felix.http.svcprop.port.secure
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
