Applications deployed to TorqueBox via 'torquebox deploy' or manual filesystem deployment must be redeployed every time EAP is restarted. If not, the .dodeploy / .deployed filesystem markers get removed and the application does not deploy on EAP restarts. This is a big usability problem for TorqueBox users. The actual EAP issue is tracked at https://issues.jboss.org/browse/JBPAPP-9328. TorqueBox 2.0.0.ER8 on top of JBoss EAP 6.0.0 GA were the versions tested that exhibit this behavior.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Applications deployed to TorqueBox via 'torquebox deploy' or manual filesystem deployment must be redeployed every time EAP is restarted. If not, the .dodeploy / .deployed filesystem markers get removed and the application does not deploy on EAP restarts. This is a big usability problem for TorqueBox users. The actual EAP issue is tracked at https://issues.jboss.org/browse/JBPAPP-9328.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Applications deployed to TorqueBox via 'torquebox deploy' or manual filesystem deployment must be redeployed every time EAP is restarted. If not, the .dodeploy / .deployed filesystem markers get removed and the application does not deploy on EAP restarts. This is a big usability problem for TorqueBox users. The actual EAP issue is tracked at https://issues.jboss.org/browse/JBPAPP-9328.+If an application deployed to TorqueBox via <command>torqebox deploy</command> or manual filestyem deployment is not deployed every time the application server is restarted, the .dodeploy and .deployed filesystem markers are removed. This means that the application will not deploy when the application server is restarted.
Andreas Eigenmann <andreas.eigenmann> made a comment on jira JBPAPP-9328 A patch would be nice, until 6.0.1.ER1 in Q4.
Andreas Eigenmann <andreas.eigenmann> made a comment on jira JBPAPP-9328 A patch for EAP 6.0.0 would be nice, until 6.0.1 in Q4.
Vladimir Rastseluev <vrastsel> updated the status of jira JBPAPP-9328 to Closed
Vladimir Rastseluev <vrastsel> made a comment on jira JBPAPP-9328 Verified on EAP 6.0.1 ER2
Sande Gilda <sgilda> made a comment on jira JBPAPP-9328 Does this need a release note for EAP 6.0.1? If so, the issue needs to be re-opened and the release notes flags set (Affects Release Notes, Not Yet Documented). If not, the issue needs to be re-opened and the release notes flag set to "Release notes not required".
Darrin Mison <dmison> updated the status of jira JBPAPP-9328 to Reopened
Darrin Mison <dmison> made a comment on jira JBPAPP-9328 reopening for release notes
Darrin Mison <dmison> updated the status of jira JBPAPP-9328 to Closed
Darrin Mison <dmison> made a comment on jira JBPAPP-9328 documented as resolved in 6.0.1
Darrin Mison <dmison> made a comment on jira JBPAPP-9328 fixed typo in release note
Darrin Mison <dmison> made a comment on jira JBPAPP-9328 sorry, removed unnecessary details from release note.
Depends on EAP 6.0.1, so is known issue for WFK 2.1
Verified on WFK 2.2.0.ER1
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.