[
https://issues.apache.org/jira/browse/FELIX-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406291#comment-17406291
]
Eric Norman commented on FELIX-6436:
------------------------------------
FYI: This appears to also change some behavior from the last release that shows
up in the a few new failing tests in the Sling Launchpad Testing module after
updating to the 4.6.4 version of webconsole.
Basically this is what I am seeing:
# If the "apply" request parameter is sent with a value of "true" then the
POST request to change the configuration now returns a 200 response code
instead of a 302 response code. Changing the test to send "apply=update" seems
to help here.
# If the "apply" request parameter is sent with any value and the posted
changes are not different from the default values or the props are empty then
no configuration is created? This seems like it could be a problem for a
component declared with "policy=ConfigurationPolicy.REQUIRE" as the component
would never get activated without a configuration.
> Exclude default values (from metatype) in Configuration
> -------------------------------------------------------
>
> Key: FELIX-6436
> URL: https://issues.apache.org/jira/browse/FELIX-6436
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: webconsole-4.6.4
>
>
> When an OSGi configuration is changed through the web console, all properties
> are set in the created/updated configuration, including those which are
> actually not set in the web console - but where just the default value is
> transfered back.
> This prohibits those configurations from using any change in the default
> values.
> The implementation could be smarter and check metatype info (if available)
> and exclude all properties with default values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
