felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3198) Support generic configuration properties
Date Thu, 03 Nov 2011 09:03:32 GMT

     [ https://issues.apache.org/jira/browse/FELIX-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Felix Meschberger resolved FELIX-3198.

       Resolution: Fixed
    Fix Version/s: http-2.2.2

Added support for generic properties in Rev. 1196998

Also implemented generic Jetty Session configuration based on this functionality for the following

 * Name of the Session cookie: org.mortbay.jetty.servlet.SessionCookie (default: JSESSIONID)
 * Name of the Session Request parameter: org.mortbay.jetty.servlet.SessionURL (default: jsessionid")
 * Domain for the session cookie: org.mortbay.jetty.servlet.SessionDomain (default: null)
 * Path for the session cookie: org.mortbay.jetty.servlet.SessionPath (default: Servlet Context
 * Max age value for the session cookie: org.mortbay.jetty.servlet.MaxAge (default: -1)

(updated the doc page for these additions)
> Support generic configuration properties
> ----------------------------------------
>                 Key: FELIX-3198
>                 URL: https://issues.apache.org/jira/browse/FELIX-3198
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>    Affects Versions: http-2.2.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: http-2.2.2
> Currently the Jetty configuration only allows for a hard-coded limited sets of properties
provided in either the Configuration Admin configuration or as framework properties.
> Adding support for generic properties allows administrators to configure the Servlet
Container more specifically. Examples of such properties would be Jetty specific session configuration.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message