[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5238) Redeployment not working after exception during deployment

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5238:
------------------------------------

Have you tried doing a full publish at that point?  

I'm assuming your deployment exception was on the server side and not an error in the tooling. If that's the case than the server does not recognize the files as a deployment and so an incremental deployment will not fix it. You must do a full publish of the module in order for the server to properly scan it for updates. 

> Redeployment not working after exception during deployment
> ----------------------------------------------------------
>
>                 Key: JBIDE-5238
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5238
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.M4
>         Environment: Win XP, JDK 1.6.0_16, JBoss 5.1 GA, Seam 2.2.0 GA, Eclipse Galileo Build id: 20090920-1017, JBoss Tools 3.1 M4
>            Reporter: Sebastian Scheid
>            Assignee: Rob Stryker
>
> JBoss has been started from within Eclipse. An ear (Seam-Project) has been added to the server. 
> If an exception occurrs during deployment of that ear, like a syntax error in components.xml or a RuntimeException during initialization of a Seam-Component, the "Touch Descriptors" command in the toolbar has no effect anymore. Any change in the xml-files in WEB-INF like web.xml, component.xml or pages.xml does not result in a redeploy either. The hot deployment of xhtml files is also corrupted in this state. 
> The only solution is to restart the Server.
> Sometimes this behaviour occurs without an exception during deployment. But it seems, that it always occurs after an exception.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira