[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5918) Seam ear project is sometimes undeployed incorrectly

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-5918:
---------------------------------------

    Fix Version/s: 3.1.1
                       (was: 3.1.0.CR2)
         Assignee: Rob Stryker


"project is removed from seam folder" ? What does that mean ?

We should only be removing content from the designated AS deploy folders - and if they are removed from there and redeploy does not happen then that is very mysteriously.

Rob, any chance that the JMX call to start scanning again is not completing and we don't show info about it ?

> Seam ear project is sometimes undeployed incorrectly
> ----------------------------------------------------
>
>                 Key: JBIDE-5918
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5918
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>         Environment: JBDS 3.0.0. #173, RHEL 5 Client, OpenJDK 1.6
>            Reporter: Jiri Peterka
>            Assignee: Rob Stryker
>             Fix For: 3.1.1
>
>
> There is strange undeployment, here is wha I did.
> 1. Install new JBDS eclipse with EAP
> 2. Start server
> 3. Create seam ear project testseam1 (everything default)
> - project is deployed and information is in the console view
> 4. Click on testseam1 project and run on the server on context menu
> - chek it in the internal browser
> 5. Click on the server in server view
> 6. Add remove and remove all 
> - project is removed from the seam folder, but no information about undeployment is present neither in console nor in log files 
> and what is strange, seam project is still accesible through eclipse web browser
> When deploy/undeploy without JBDS it works fine. I was able to duplicate this only on RHEL and not everytime. Usually for the first time with clean installation.
> It's not critical because after some time or eclipse restart it works normal. 

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