Carsten Ziegeler created FELIX-6453:
---------------------------------------
Summary: Change in configuration handling introduces by FELIX-6436
Key: FELIX-6453
URL: https://issues.apache.org/jira/browse/FELIX-6453
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.6.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: webconsole-4.7.0
>From FELIX-6436 by [~enorman]:
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
