Community
Participate
Working Groups
If a security manager is set, our performance degrades by 200%. This is because of our doPriviledge. Currently our test scripts set a security manager by default. We should not enable doPrivilege by default if a security manager is set, a system property should be required to enable it. We need to know what environments set this by default, it seems that OC4J, or probably OracleAS may set this by default. Most likely other servers set this as well giving us 200% worse performance than other products. Also the current system property to disable it was not renamed and is still oracle.toplink.
SVN: Checkin bug#220815 don't use do privilege unless set Changes: - Changed the doPrivilege to only be used if the system property is set, and renamed property from toplink to "eclipselink.secuirty.usedoprivilege". Code Review: Tom (pending)
Created attachment 97027 [details] patch
This will avoid people accidentally loosing 200% performance when using a security manager. Since additional configuration is required to use doPrivilege requiring the property to be set should be no big issue. OC4J may need to set this when integrating with EclipseLink when using a security manager.
closing
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink