Bug 1012057

Summary: [eap6]: Cannot create new deployment scanner
Product: [JBoss] JBoss Operations Network Reporter: Jan Stefl <jstefl>
Component: Plugin -- JBoss EAP 6Assignee: Libor Zoubek <lzoubek>
Status: CLOSED NOTABUG QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jstefl, lzoubek, myarboro, rhatlapa, theute
Target Milestone: ---   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-30 14:16:54 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Stefl 2013-09-25 15:46:38 UTC 
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.
Comment 1 Jan Stefl 2013-09-26 08:41:16 UTC 
I found out, that directory (deployDir2) has to be created manually.

Nevertheless
 - JON should notice me that operation was not successful.
Comment 2 Jan Stefl 2013-10-04 13:48:50 UTC 
Ok, we can postpone this to JON 3.3.0.
Comment 3 Jan Stefl 2013-10-04 13:51:42 UTC 
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.
Comment 4 Libor Zoubek 2014-07-08 15:49:41 UTC 
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.
Comment 5 Radim Hatlapatka 2014-07-30 14:16:54 UTC 
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.