Update farmed Application Deployment (EAR/WAR) results in non-farmed deployment

1. Setup a two node EAP cluster 2. Deploy an application (EAR/WAR) to node1's farm using admin-console 3. Verify application was deployed to both node1 and node2 4. Update the application using the same EAR/WAR (From admin-console, expand and select the deployed EAR/WAR and select it's Content tab and then click Update) Actual results: The updated deployed application is now only deployed to node1 in its deploy directory Expected results: The updated deployed application is deployed to node1 and node2 and appears in their farm directory Edit: This bug appears in the RHQ jboss-as-5 plugin code, and as such has had the Component and Assignee updated.

When using the admin-console to update an application (EAR or WAR) deployed to the farm directory, the target application would be removed from the farm directory and deployed to the deploy directory. This would result in the application being removed from the other members of a cluster that utilized the farm directory to distribute the application. This issue is resolved by ensuring that an application that is being updated and is in the farm directory to start with, remains in the farm directory after the update.