[jbosstools-issues] [JBoss JIRA] (JBIDE-10023) When hot code replace fails, offer "restart deployment "as an alternative

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-10023:
---------------------------------------

We can add a hot replacement dialog (or replace the standard Eclipse dialog) that would be activated for JBoss AS launch configurations using the API Max pointed to.

I suppose we have to do the following:

1) if out of sync class(es) is part of a Seam project and is in the WEB-INF/dev directory, we wouldn't show the dialog. This feature would require using Java Reflection.

2) offer the same actions as those the standard Eclipse dialog contains and the "restart deployment(s)" action
The "restart deployment" action could do the following:

- restart all deployed modules
or
- restart only those modules that contain the replaced class(es) that is out of sync. The feature would require Java Reflection.

The "restart deployment" action would continue the session after that.

The dialog would include the "Remember my decision" checkbox.

3) add a preference that would enable/disable this feature. I suppose it would be disabled by default.

WDYT?

                
> When hot code replace fails, offer "restart deployment "as an alternative
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-10023
>                 URL: https://issues.jboss.org/browse/JBIDE-10023
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>            Reporter: Gavin King
>            Assignee: Snjezana Peco
>            Priority: Optional
>             Fix For: 4.0.x
>
>
> The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative.

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