[
https://issues.apache.org/jira/browse/FELIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174949#comment-14174949
]
Carsten Ziegeler commented on FELIX-3817:
-----------------------------------------
[~v_valchev] That would work I agree. People using the api need to be aware of
the special parameters in order to prefix their configuration values correctly.
What if we do it the other way round? Unless you have a name class, everything
stays as is - if you have a class, you prefix the command parameters to $, so
the configuration name would still be appy="Configuration Value" but
$apply=true for the rest api.
> Form parameters might clash with configuration parameters
> ---------------------------------------------------------
>
> Key: FELIX-3817
> URL: https://issues.apache.org/jira/browse/FELIX-3817
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-4.0.0
> Reporter: Carsten Ziegeler
> Fix For: webconsole-4.2.4
>
> Attachments: webconsole-FELIX-3817.patch
>
>
> If a configuration has a property named "delete" or "propertylist" (and maybe
> there are more) then this clashes with the form parameter names of the
> configuration web console plugin and editing such a configuration is not
> possible.
> We should use more unique names, maybe namespaced somehow to reduce the
> potential of a name clash
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
