Scenario Agent -> JBoss EAP Standalone Server -> (my instance) -> deployment scanner -> resource configuration (right click) -> + : name = deployDir2 path = deployDir2 relativeTo = jboss.server.base.dir -> Ok -> Save -> Refresh New scanner is not saved (doesn't exists in JON nor EAP instance). The issue was discovered on Windows, jdk17 but it is possible that is more general.
I found out, that directory (deployDir2) has to be created manually. Nevertheless - JON should notice me that operation was not successful.
Ok, we can postpone this to JON 3.3.0.
Why do you think this is an enhancement. EAP informs you that directory does not exist, I think JON should create missing directory based on EAP response.
I think this could be closed as NOTABUG. when configuration update fails in JON, user can find out by looking at configuration update history. I don't think JON should create missing directory and workaround fact, that EAP is not able to create directory itself.
Libor, I agree with you, closing as NOTABUG. Discussed also with Honza (jstefl), who agrees, He just didn't notice the failure message in configuration history.