Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.1.2, 5.2.2
-
Component/s: None
-
Labels:None
-
Branch Version/s:5.1.x
-
Backported to Branch:Committed
-
Similar Issues:
Description
PortletExplodedTomcatListener is being used to support directory deployment through Portal Pack NetBeans Plug-in. By using this feature, instead of war file, the build directory of the project inside NetBeans gets deployed to the appserver. And any changes in the JSP/javascripts are automatically picked up by the glassfish/tomcat appserver without any redeployment.
PortletExplodedTomcatListener is currently doing the following things
1. Massage the exploded directory
2. Then copy context xml to tomcat's conf directory (Which is required for the deployment of portlet app on tomcat)
But the second step is not required when the appserver type is Glassfish. Currently the copyContextFile() copies the context xml file to Glassfish's domain1/conf directory. Because of that glassfish is throwing exception during every deployment (Though the exception is harmless).
Fix :
- In PortletExplodedTomcatListener, don't copy context xml file if the appserver type is glassfish.

Modified the logic to be ServerDetector.isTomcat instead of !ServerDetector.isGlassfish