Hi Ray
What would be the best way to find out which declarations are missing in liferay-plugin-package.propeties.
At the moment, all we get with security-manager-enabled=true during deploy time is:
103:03:28,552 WARN [pool-2-thread-3][RuntimeChecker:256] Attempted to access declared members
203:03:28,556 ERROR [pool-2-thread-3][BasePortalLifecycle:45] javax.servlet.UnavailableException
3javax.servlet.UnavailableException
4 at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:880)
5 at org.apache.portals.bridges.struts.PortletServlet.initModulePlugIns(PortletServlet.java:121)
6 at org.apache.struts.action.ActionServlet.init(ActionServlet.java:336)
7 at javax.servlet.GenericServlet.init(GenericServlet.java:160)
8 at org.apache.portals.bridges.struts.PortletServlet.init(PortletServlet.java:55)
9 at com.liferay.portal.kernel.servlet.SecureServlet.doPortalInit(SecureServlet.java:95)
10 at com.liferay.portal.kernel.util.BasePortalLifecycle.portalInit(BasePortalLifecycle.java:42)
This is a very large enterprise-scale portlet (liferay struts-based) with access to external services, there could be too many of points of security crossings so blind copying of of configuration from existing marketplace applications would not bring much help.
And in this specific case I assume that security manager has not even reached our implementation classes yet, portlet fails to deploy.
Some static initalizations in Liferay struts bridges?
Ray, would you
suggest any debugging/workaround tips, may be we can override some of your classes to produce a better stack trace?
-------------------------------------------
EDITED: I attempted to have a look how Liferay configures own portlets for Security Manager, so I 'purchased' Web Form CE, had a look inside and found that it is not set for use under PACL at all.
PS. Is it also feasible for Liferay to bundle all own portlets with security features, so at least two positive outcomes can be achieved:
1). Marketplace App developers can see how it should be done in real applications, not just in primitive test/demo cases
2). If Liferay cannot make own portlets to work with PACL, more resources will be thrown into this area.
Please sign in to flag this as inappropriate.