[
https://issues.apache.org/jira/browse/FELIX-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025681#comment-14025681
]
Karl Pauls commented on FELIX-4528:
-----------------------------------
FWIW, you actually should be able to do what you want with the current main
launcher using property substitution e.g.:
add in conf/config.properties
felix.extension.disable=${jnlp.felix.extension.disable}
> Felix properties cannot be used in unsigned JNLP files
> ------------------------------------------------------
>
> Key: FELIX-4528
> URL: https://issues.apache.org/jira/browse/FELIX-4528
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Environment: java 7u45 and later
> Reporter: Rob Walker
> Assignee: Rob Walker
> Priority: Minor
> Attachments: sec_action.patch
>
>
> Unsigned JNLP files are required for most real world cases - especially those
> with dynamic deployment needs where the host URL cannot be known in advance.
> To use System properties in unsigned JNLP files they must be prefixed with
> "jnlp." - which effectively renders all current Felix properties unusable.
> Attached is a patch with one implementation approach for this - a mod to
> SecureAction to check for a "jnlp," version of a property before falling back
> to System properties or the supplied default.
> An alternative would be additional init code in Felix or FelixConstants to
> test each property that we wish to expose to JNLP files and push any non-null
> value into System properties. This would be more transparent, but also more
> maintenance whenever new FelixConstants are added.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
