[jira] [Commented] (FELIX-4061) Implement service endpoint registration property
[ https://issues.apache.org/jira/browse/FELIX-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320028#comment-14320028 ] Carsten Ziegeler commented on FELIX-4061: - Updated to the latest spec in 1659544 while keeping compatibility with previous versions > Implement service endpoint registration property > > > Key: FELIX-4061 > URL: https://issues.apache.org/jira/browse/FELIX-4061 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http-2.2.2 > > > In section 5.1.5.1 of the early draft 2013.03 it reads: > The Http Service must expose the following information through its servlet > registration properties: > osgi.http.service.endpoints : A String+ property listing URLs of bound ports; > e.g. http://192.168.1.10:8080/. The relevant information contained in the > URLs is the scheme, bound interface and port and the (optional) context path > in a Servlet API servlet container the Http Service is registered. > The port and address properties may not always be available to the Http > Service implementation, particularly in a > bridged implementation. In such cases these properties may be omitted from > the service registration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4061) Implement service endpoint registration property
[ https://issues.apache.org/jira/browse/FELIX-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656897#comment-13656897 ] Carsten Ziegeler commented on FELIX-4061: - I've added first implementation in revision 1482253 for the jetty implementation. > Implement service endpoint registration property > > > Key: FELIX-4061 > URL: https://issues.apache.org/jira/browse/FELIX-4061 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http-2.2.2 > > > In section 5.1.5.1 of the early draft 2013.03 it reads: > The Http Service must expose the following information through its servlet > registration properties: > osgi.http.service.endpoints : A String+ property listing URLs of bound ports; > e.g. http://192.168.1.10:8080/. The relevant information contained in the > URLs is the scheme, bound interface and port and the (optional) context path > in a Servlet API servlet container the Http Service is registered. > The port and address properties may not always be available to the Http > Service implementation, particularly in a > bridged implementation. In such cases these properties may be omitted from > the service registration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-4061) Implement service endpoint registration property
[ https://issues.apache.org/jira/browse/FELIX-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654570#comment-13654570 ] Carsten Ziegeler commented on FELIX-4061: - Implemented a way of the http bridge in revision 1481070: It uses the framework property "org.apache.felix.http.service.endpoints" to set the "osgi.http.service.endpoints" property - in a bridged environment like running in a web application server, there is no way of finding out to which address and port the server is bound; especially not without a request object. > Implement service endpoint registration property > > > Key: FELIX-4061 > URL: https://issues.apache.org/jira/browse/FELIX-4061 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler > Fix For: http-2.2.2 > > > In section 5.1.5.1 of the early draft 2013.03 it reads: > The Http Service must expose the following information through its servlet > registration properties: > osgi.http.service.endpoints : A String+ property listing URLs of bound ports; > e.g. http://192.168.1.10:8080/. The relevant information contained in the > URLs is the scheme, bound interface and port and the (optional) context path > in a Servlet API servlet container the Http Service is registered. > The port and address properties may not always be available to the Http > Service implementation, particularly in a > bridged implementation. In such cases these properties may be omitted from > the service registration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira