DeployManager on jetty fails to undeploy

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.0.X EE
• Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1, 6.0.X EE
• Component/s: -- none --
• Labels:
  • QA-R
• Similar Issues: Show 5 results ; ;

  LPS-19983	DeployManager to alloy Jetty to redeploy
  LPS-19062	DeployManager fails to deploy themes and some portlets
  LPS-18997	DeployManager fails to copy all dependencies when deploying a portlet
  LPS-26361	Jetty: Social Bookmarks is not completely undeployed
  LPS-24282	Can't undeploy sample-icefaces-jsf-1.1-myfaces-jsp-portlet in Jetty

There are the following problems with deploying/undeploying via DeployManagerUtil on Jetty.

1. When running on Jetty the DeployManager (DeployManagerUtil) deploys successfully but copies the context xml file for the deployable to the context directory under the name jetty-context-configure.xml instead of the name of the context. This causes the undeploy not to find the context file.

2. The DeployUtil.undeploy method returns immediately, without undeploying, unless the app server is Tomcat or JBoss. It should also accept Jetty.

3. The DeployUtil.undeploy method ignores the appServerType parameter for some checks and instead uses ServerDetector.isTomcat/isJetty/etc. This is theoretically incorrect because the caller will expect the appServerType parameter to be honored even if it is not the app server currently running, and it is practically incorrect because it will fail when called from Ant.

[Brian Chan]

Very good comments Jon.

[Vicki Tsang]

This is being bulk closed in preparation for the new workflow.