Bindings of most binding-types can not be created in naming subsystem configuration in Web Console -------------------------------------------------------------------------------------------------- Key: WFLY-6754 URL: https://issues.jboss.org/browse/WFLY-6754 Project: WildFly Issue Type: Bug Components: Naming, Web Console Affects Versions: 10.0.0.Final Reporter: Tomas Hofman Assignee: Tomas Hofman Priority: Critical When adding bindings in naming subsystem configuration of Web Console, the Add form has wrong mandatory fields. Mandatory fields for bindings are dependent on binding type. On the other hand, some binding types do not have attributes that the Add form will try to send to the interface, resulting in user being unable to add any binding type besides {{external context}} (for example, adding a simple or lookup binding will result in {{Unknown error}} due to simple binding type not being able to have 'cache' attribute). For example, {{/subsystem=naming/binding=java\:global\/a:add(binding-type=simple, type=int, value=100)}} would be a legal simple binding inserted through the JBoss CLI: {code}{"outcome" => "success"}{code} Adding this same following binding will produce the following error output in Web Console: {quote}Unknown error Unexpected HTTP response: 500 Request {code}{ "name" => "java:global/a", "binding-type" => "simple", "cache" => false, "class" => undefined, "environment" => undefined, "lookup" => undefined, "module" => undefined, "type" => "int", "value" => "100", "operation" => "add", "address" => [ ("subsystem" => "naming"), ("binding" => "java:global/a") ] }{code} Response Internal Server Error {code}{ "outcome" => "failed", "failure-description" => "WFLYNAM0061: Binding type simple can not take a 'cache' attribute", "rolled-back" => true }{code}{quote}