Summary: Liferay looses the reference to the context.xml during hot deploy in case it has been suspended by the deployment order functionality.
Initial setup: I'm using Liferay 6.2 GA2 bundled with tomcat. I have portlet A and hook B and portlet A shall be deployed after hook A (using required-deployment-contexts=b-hook setting in liferay-plugin-package.properties file of portlet A). Additionally i have configured the setting portlet.resource.id.banned.paths.regexp=.*/(?:WEB-INF)/.* inside portal-ext.properties so that the context.xml inside folder META-INF will be preserved.
Detailed Problem description:
After starting liferay the ROOT web app (Liferay) will be loaded.
Afterwards the portal tries to deploy portlet A and discover that portlet A must be queued up.
Then hook B will be deployed.
After hook B has been deployed, deploying of portlet A will be continued. And here we have the problem that calling new InitialContext() inside a ServletContextListener refers now to the configurations defined in the context.xml of hook B instead of using the context.xml of portlet A
Question: What can be done to get the context of portlet A?
The problem is, that without specifying portlet.resource.id.banned.paths.regexp=.*/(?:WEB-INF)/.* the original context.xml will be replaces by a liferay generated one.
