[
https://issues.apache.org/jira/browse/FELIX-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026402#comment-14026402
]
Richard S. Hall commented on FELIX-4528:
----------------------------------------
Admittedly, there are special cases handled in the framework, but typically
those are there to get the framework to run properly/better on a given
platform, not to get them to run with various frameworks on a given platform.
Sometimes this line can be fuzzy, but we try to be consistent. The idea is that
there are a lot fewer platforms to support than frameworks.
Regarding having the project structure to provide these modules, I think we do
have such a structure, we just need people to create launcher subprojects for
special use cases.
> 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
> 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)
