felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-784) Create "felix" property name as alternatives to old style Oscar property names
Date Tue, 27 Jan 2009 21:14:59 GMT

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

Marcel Offermans resolved FELIX-784.

    Resolution: Fixed

Implemented as documented in the svn commit. New properties take precedence over old ones
if both are specified.

> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>                 Key: FELIX-784
>                 URL: https://issues.apache.org/jira/browse/FELIX-784
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>            Reporter: Rob Walker
>            Assignee: Marcel Offermans
>            Priority: Trivial
> Some of the Http properties still use the old Oscar prefix. 
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable  ----->   org.apache.felix.https.enable  
> org.ungoverned.osgi.bundle.https.provider  ----->   org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore  ----->   org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password  ----->   org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password  ----->   org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug  ----->   org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty
it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives
in parallel to the older style name, so either name may be used.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message