Combination View Flat View Tree View
toggle
Philippe Tran
PACL and "Attempted to access declared members"
July 1, 2013 5:15 PM
Answer

Philippe Tran

Rank: Junior Member

Posts: 34

Join Date: January 22, 2009

Recent Posts

Hi everyone,

I'm facing this warning "Attempted to access declared members" when my portlet app (ex: myapp.war, containing several portlets) starts up, with Security Manager enabled on Liferay 6.2.0 M5 and M6.

The message is fired by a call to getDeclaredMethods() made by org.springframework.core.convert.support.IdToEntityConverter in webapps/myapp/WEB-INF/lib/org.springframework.core-3.0.7.RELEASE.jar.

After reading the doc at here and there, I still don't understand how to get rid of this warning.

My problem seems analog to LPS-31182, with a difference: the caller is in a jar from my war file.

I tried:

security-manager-class-loader-reference-ids=myapp
security-manager-get-bean-property=org.springframework.core.convert.support.IdToEntityConverter


I tried also to define a java.policy in WEB-INF with:

grant codeBase "file:${myapp}${/}-" {
permission java.lang.RuntimePermission "accessDeclaredMembers";
};


But the warning is still there. Unfortunately, the security-manager generate option doesn't help. Does anyone have any clue about his ?

Thanks in advance,
Philippe
Ray Augé
RE: PACL and "Attempted to access declared members"
July 2, 2013 7:57 AM
Answer

Ray Augé

LIFERAY STAFF

Rank: Liferay Legend

Posts: 1238

Join Date: February 7, 2005

Recent Posts

Sorry, but the warning will not currently go away even after you add the correct java.policy, which you have.

This is due to a current design limitation that we haven't had time to refactor yet.

However, the app "should" work properly.

Is that not the case?
Philippe Tran
RE: PACL and "Attempted to access declared members"
July 10, 2013 12:39 AM
Answer

Philippe Tran

Rank: Junior Member

Posts: 34

Join Date: January 22, 2009

Recent Posts

Hi Ray,

Thank you for your answer. In fact, I found a way to by-pass the Spring getDeclaredMethods() method call, and I don't get this warning anymore.

Thanks again,
Philippe