Exploded deploy a portlet failed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: No Longer Reproducible
• Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
• Fix Version/s: 6.2.0 CE M4
• Component/s: API, API > JavaScript
• Labels:
  • community-verifier
• Environment: 6.1.10 EE GA1 ; ; Tomcat 7.0.25, JBoss 7.0.2, MySQL 5.1
• Similar Issues: Show 5 results ; ;

  LPS-35085	exploded directory deployment for portlet on tomcat fails to init after restart of server
  LPS-24212	Exploded portlet deployer with service builder portlet fails
  LPS-28827	test-pacl-portlet - Distinguish between an exploded and unexploded war file
  LPS-9118	Add support for exploded directory deployment of hook plugins for tomcat server
  LPS-1228	For Exploded Directory Deployment, war directory is not getting massaged properly when portlet.container.implementation=sun

Exploded deploy a portlet failed

Use cases:
1) take note about a plugin knowledge-base-portlet web.xml
2) deploy the plugin knowledge-base-portlet WAR file. The portal will change plugin's web.xml
3) copy the modified web.xml back to the plugin
4) generate WAR and deploy it again.

The portal throws errors.

[Aniceto P Madrid]

Jonas
After the fist deployment, knowledge-base worked fine or not? Which are the changes made in web.xml? Why do you update the war?
Thanks

[Aniceto P Madrid]

I couldn't understand neither reporter did those actions nor what changed and caused the fail.
Besides, this the reporter has not answered requests for more than 10 days. So I suggest to close this issue.