jboss-admin.sh accepts crazy values for :add-proxy()

I am allowed to use all of these kinds of syntax with :add-proxy():

[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=abc.com,port=123)
{
"outcome" => "success",
"result" => {
"domain-results" =>

{"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"port" => 123,
"host" => "abc.com",
"operation-headers" => {"execute-for-coordinator" => true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(host=def.com)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined}

,
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"host" => "def.com",
"operation-headers" =>

{"execute-for-coordinator" => true}
}
}]
}
}
[domain@localhost:9999 subsystem=modcluster] :add-proxy(port=999)
{
"outcome" => "success",
"result" => {
"domain-results" => {"step-1" => undefined},
"server-operations" => [{
"servers" => [],
"operation" => {
"address" => [("subsystem" => "modcluster")],
"operation" => "add-proxy",
"port" => 999,
"operation-headers" => {"execute-for-coordinator" => true}

}
}]
}
}

I think only the first one should be valid.