[jboss-jira] [JBoss JIRA] (WFLY-5764) Remove the default value with outdated contexts for mod_cluster's excluded-context

[Radoslav Husar (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radoslav Husar updated WFLY-5764:
---------------------------------
    Description: 
The list of current values is useless in the defualt configuration.

{code}"excluded-contexts" => "ROOT,invoker,jbossws,juddi,console"{code}

I am actually marking this as bug, because if you just want to use the root context, if you undefine the value, the default will be used which exludes root context.

Trying a "" value, results in a failure.

{code}[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value=""
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0113: '' is an invalid value for parameter excluded-contexts. Values must have a minimum length of 1 characters",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}{code}

This all comes from legacy stuff.

  was:
The list of current values is useless in the defualt configuration.

{code}        "excluded-contexts" => "ROOT,invoker,jbossws,juddi,console",{code}

I am actually marking this as bug, because if you just want to use the root context, if you undefine the value, the default will be used which exludes root context.

Trying a "" value, results in a failure.

{code}[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value=""
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0113: '' is an invalid value for parameter excluded-contexts. Values must have a minimum length of 1 characters",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}{code}

This all comes from legacy stuff.



> Remove the default value with outdated contexts for mod_cluster's excluded-context
> ----------------------------------------------------------------------------------
>
>                 Key: WFLY-5764
>                 URL: https://issues.jboss.org/browse/WFLY-5764
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.CR4
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>
> The list of current values is useless in the defualt configuration.
> {code}"excluded-contexts" => "ROOT,invoker,jbossws,juddi,console"{code}
> I am actually marking this as bug, because if you just want to use the root context, if you undefine the value, the default will be used which exludes root context.
> Trying a "" value, results in a failure.
> {code}[standalone at localhost:9990 /] /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=excluded-contexts,value=""
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0113: '' is an invalid value for parameter excluded-contexts. Values must have a minimum length of 1 characters",
>     "rolled-back" => true,
>     "response-headers" => {"process-state" => "reload-required"}
> }{code}
> This all comes from legacy stuff.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)