felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4528) Felix properties cannot be used in unsigned JNLP files
Date Mon, 09 Jun 2014 20:13:03 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025675#comment-14025675

Richard S. Hall commented on FELIX-4528:

I understand your argument, but this was precisely the reason why we always tried to keep
launching issues separate from the framework implementation, so that we don't need to insert
any n-line changes for arbitrary launching purposes since everyone always views their own
launching use case as more of a requirement than someone else's.

At a minimum, this seems like you should be proposing a feature request against Main, which
is the launcher, as opposed to the framework implementation. Even then, we've still largely
maintained that Main was more of a simple, general purpose launcher and not meant to handle
all cases.

Yet another approach is to simply create a new Felix subproject for a JNLP-specific launcher
that has all the bells and whistles necessary to easily use the Felix framework within JNLP.

> 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

This message was sent by Atlassian JIRA

View raw message