PACL incompatibility with JSF portlets

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
• Fix Version/s: 6.1.X EE, 6.2.0 CE M4
• Component/s: Security, Security > PACL
• Labels: None
• Environment: N/A
• Similar Issues: Show 5 results ; ;

  LPS-32623	PACL incompatibility with MacOS X JDK
  LPS-12063	Incompatibility with WebLogic 10.3.1, JSF 1.2 R.I. and MyFaces Portlet Bridge 1.0.0
  LPS-26796	WSRP incompatibility with JSF portlets due to empty request parameters getting ignored
  LPS-34863	PACL AccessControlException with Mojarra JSF portlets with @PostConstruct annotated managed-bean methods
  LPS-17234	Update JSF Portlet template with JSF 2.1, ICEfaces 2.0.2 update

When a portlet tries to perform reflection, the PACL BaseReflectChecker class is consulted to see if the class is permitted to do so. With frameworks like JSF, there is quite a bit of reflection happening during startup/shutdown time, and also during processing of requests. Each of these attempts to reflect are failing with PACL, because the BaseReflectChecker class has no knowledge of these special cases for JSF.

[Neil Griffin]

This issue can be closed – it is a duplicate in the sense that Ray Auge's reflection refactoring of PACL will fix these problems.