[jbosstools-issues] [JBoss JIRA] (JBIDE-13444) deployment scanner additions should be called from behavior

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-13444.
---------------------------------

    Resolution: Done


This is in master now. One other effect of this is that the startup activators do not need to add these global listeners, which also helps our other goal of moving logic out of our activators and into more reasonable locations. 
                
> deployment scanner additions should be called from behavior
> -----------------------------------------------------------
>
>                 Key: JBIDE-13444
>                 URL: https://issues.jboss.org/browse/JBIDE-13444
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS/Servers
>    Affects Versions: 4.0.0.Final
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.1.0.Alpha1
>
>
> The classes in charge of adding deployment scanners to a running server are currently responding to the wtp framework's alert that the server has started. In this way, they are listeners, listening to every server event, and choosing to only respond to events where a server is set to 'started'. 
> This is not the best solution and is a little un-intuitive. It would be more reasonable if the behavior (or its delegate) initiated this activity rather than going through the framework listeners. 
> Luckily, almost the API already exists to move these classes solely into as.core. as.core already has an extension point to locate a jmx runner from the as.jmx.integration code and has used it in the past to suspend deployment scanners and resume them during a publish event. 
> The class handling as7 via management also exists in as.core (or at least the method to FIND the management does), and so this requires no large changes. 
> Tasks: 
> 1) Move the JMX deployment scanner additions into as.core
> 2) Modify both jmx and as7's deployment scanner listeners to no longer be listeners, and make them accessible via the ServerExtendedPRoperties internal api. 
> 3) Ensure the behaviors or their delegates call this once they set the server to started. 

--
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