[jbosstools-issues] [JBoss JIRA] (JBIDE-13207) Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767237#comment-12767237 ] 

Martin Malina commented on JBIDE-13207:
---------------------------------------

Rob asked me to try again since it worked for him. So I did.
1. I started with a new workspace and added EAP 6.0.1 with its scanner set for 0
2. After server was started I was asked if I want to change the inactive scanner - I changed it to 5000 and it changed the value in the file immediately - FINE
3. I stopped the server and changed the value in standalone.xml to 0 again
4. I started the server and when asked about the inactive scanner, I canceled it - standalone.xml remained intact - FINE
5. I stopped the server
6. I started the server and when asked about the inactive scanner, I changed the value to 5000 and hit OK, but nothing changed - FAIL
                
> Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13207
>                 URL: https://issues.jboss.org/browse/JBIDE-13207
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>         Environment: 
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>             Fix For: 4.1.0.Alpha2
>
>         Attachments: interval-0.png
>
>
> Create EAP 6.0 runtime server make sure it has a  defaeult scanner interval of "0".
> Start EAP 6.0
> Wait N seconds/do other stuff.
> Up comes a dialog saying:
> Inactive Deployment Scanner?
> Warning: One or more deployments scanners have scan-interval of 0.
> These scanners are inactive. If this is intentional, press 'Ok'
> And then there is a table witha  scanner name and then an editable scanner interval.
> 1) There is *zero* infon on what this relates to - I would have expected at least a reference to the name of the server there is a problem with.
> 2) The dialog says I should press Ok if i'm ok - but there is no cancel button or instructions on what I otherwise can do.
> 3) The title talks about "scan-interval" the table says "Scanner Interval"
> 4) When changing the value and then closing the dialog with the red button or escape -> changes made to the config xml file - BAD!
> Suggestion:
> Title: Inactive Deployment Scanner found
> subtitle: Inactive Deployment scanner found
> Text: 'servername' contains one or more deployment scanners that are currently inactive (scan-interval=0).
> This means their folds will not be scanned for new deployments nor changes. If this is intentional, presss 'Ok',
> or if you want a different interval (recommended is: <thedefaultnumber>s ) change it in the table below and then press 'Ok'.
> Table: show the actual location the scanner is related to - otherwise users have no idea/context what scanner it is.
> Ok
> and if user press Escape or closes dialog without pressing ok -> no changes made anywhere!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira