CLI pretends that it's possible to change JDBC job repository JNDI name even for in-memory repository type

[standalone@localhost:9990 /] /subsystem=batch:read-attribute(name=job-repository-type)
{
    "outcome" => "success",
    "result" => "in-memory"
}
[standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:write-attribute(name=jndi-name,value=java:jboss/datasources/ExampleDS)
{
    "outcome" => "success",
    "response-headers" => {
        "operation-requires-reload" => true,
        "process-state" => "reload-required"
    }
}
[standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:read-attribute(name=jndi-name)
{
    "outcome" => "success",
    "result" => "java:jboss/datasources/ExampleDS",
    "response-headers" => {"process-state" => "reload-required"}
}
[standalone@localhost:9990 /] :reload
{
    "outcome" => "success",
    "result" => undefined
}
[standalone@localhost:9990 /] /subsystem=batch/job-repository=jdbc:read-attribute(name=jndi-name)
{
    "outcome" => "success",
    "result" => undefined
}