Not a blocker as at least standalone has no properties defined.

Support for reading of properties and paths is now in as7plugin branch.
Writing still needs to be done.

Setting priority on enhancements to as7 plugin to high. They don't block the JON3 release, but will be needed for subsequent release

bb1f35f5994 in master allows to edit system-properties and paths for standalone, host controller and hosts.

verified on standalone 
on DomainController I always get https://bugzilla.redhat.com/show_bug.cgi?id=784590

*** Bug 734141 has been marked as a duplicate of this bug. ***

Mark as fixed - further work on comment #5 will be done in Bug 784590

I've just tried to reproduce 784590 and I failed to add system property on DomainController on today's master build level with following result. 

Operation  returned unparsable JSON, <{"outcome":"success","result":{"step-1":{"outcome":"success"},"step-2":{"outcome":"success"},"server-groups":{"main-server-group":{"server-one":{"host":"master","response":{"outcome":"success","result":{"step-1":{"outcome":"success","response-headers":{"operation-requires-restart":true}},"step-2":{"outcome":"success"}},"response-headers":{"process-state":"restart-required"}}},"server-two":{"host":"master","response":{"outcome":"success","result":{"step-1":{"outcome":"success","response-headers":{"operation-requires-restart":true}},"step-2":{"outcome":"success"}},"response-headers":{"process-state":"restart-required"}}}}}},"server-groups":{"main-server-group":{"server-one":{"host":"master","response":{"outcome":"success","result":{"step-1":{"outcome":"success","response-headers":{"operation-requires-restart":true}},"step-2":{"outcome":"success"}},"response-headers":{"process-state":"restart-required"}}},"server-two":{"host":"master","response":{"outcome":"success","result":{"step-1":{"outcome":"success","response-headers":{"operation-requires-restart":true}},"step-2":{"outcome":"success"}},"response-headers":{"process-state":"restart-required"}}}}}}>., rolled-back=false

I used EAP6 ER1, they probably changed response message format.

master    37eea22e7b7
release-4.3.0.GA   8471ffb070e6a

Hi Heiko, 

I am not sure whether it is required or not, but I found out we're missing handling system properties at managed host level as it is described here https://community.jboss.org/wiki/JBossAS7SystemProperties. Currently on master there is no 'Configuration' tab on managed server resource.

Editing system-property (called prop) for standalone mode (EAP6 Beta1) started to fail - on 4.4 master f537827

{JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-1=JBAS014792: Unknown attribute boot-time}}, rolled-back=true

Beta 1 is too old. Please try with ER4.1

[domain@localhost:9999 /] ./system-property=foo:read-operation-description(name=add)
{
    "outcome" => "success",
    "result" => {
        "operation-name" => "add",
        "description" => "Adds a system property or updates an existing one.",
        "request-properties" => {
            "value" => {
                "type" => STRING,
                "description" => "The value of the system property.",
                "required" => false,
                "nillable" => true
            },
            "boot-time" => {
                "type" => STRING,
                "description" => "If true the system property is passed on the command-line to the started server jvm. If false, it will be pushed to the server as part of the startup sequence.",
                "required" => false,
                "nillable" => true,
                "default" => true
            }
        },
        "reply-properties" => {},
        "read-only" => false
    }
}

Editing system-property (called prop) for standalone mode (EAP6 ER4.1) still fails - Build Number: 04f2ffc

result is:

{JBAS014653: Composite operation failed and was rolled back. Steps that
failed:={Operation step-1=JBAS014792: Unknown attribute boot-time}},
rolled-back=true

Adding a system property fails for Managed server
EAP6 ER5
Version: 4.4.0-SNAPSHOT
Build Number: 0fe1b14

When saving new configuration, I get: 

{domain-failure-description={JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-2=JBAS014792: Unknown attribute jmv}}}, rolled-back=true

master 3e9a571

This was caused because of JVM selection not working as it was before. See Bug 813214

Editing system-property (called prop) for standalone mode (EAP6 ER5) still
fails - Build Number: 28e565c

result is:

{JBAS014653: Composite operation failed and was rolled back. Steps that
failed:={Operation step-1=JBAS014792: Unknown attribute boot-time}},
rolled-back=true

boot time flag does not exist on standalone servers.
Made the type boolean 

master 58dd8873d89

Build Number: 5ffafd2
There are still issues with system properties:

1. Adding system property on Standalone level works fine, but, it is ignored property name. After I add property called 'prop' with value 'val' and save configuration suddenly property is called 'value'. An attempt to add 2nd property (called 'prop2')results in having 2 properties called 'value' in UI but properties 'value' and 'prop2' on EAP. And 'boot-time' attribute still appears in UI.

2. Adding a system property started to fail on domain mode

{domain-failure-description={JBAS014653: Composite operation failed and was rolled back. Steps that failed:={Operation step-1=JBAS014688: Wrong type for boot-time. Expected [BOOLEAN] but was STRING}}}, rolled-back=true

3. On Domain Controller level java.net.preferIPv4Stack (which is defined by default) is no longer shown in UI, instead UI shows property called 'value'


A Mixture of above happens on managed server level - Adding one property results to presenting its name as 'value' when adding 2nd property I get same error as 2.

Oh .. sorry,  5ffafd2 is older than your last push, please ignore Comment 18

<pilhuhn> lzoubek no, I also see that now. This was no issue a few days ago

This was caused by commit 828678db
and is reverted now

master c17fb14

Bulk close of old bugs in VERIFIED state.