2
0

upgrade-06-070.html 2.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. <html>
  2. <head>
  3. <title>Acegi Security - Upgrading from version 0.6 to 0.7</title>
  4. </head>
  5. <body>
  6. <h1>Upgrading from 0.6 to 0.7.0</h1>
  7. <p>
  8. The following should help most casual users of the project update their
  9. applications:
  10. <ul>
  11. <li>MethodDefinitionMap, which is usually used by MethodSecurityInterceptor
  12. for its objectDefinitionSource property, has been changed. From 0.7, when
  13. MethodDefinitionMap is queried for configuration attributes associated with
  14. secure MethodInvocations, it will use any method matching in the method
  15. invocation class (as it always has) plus any method matching any interface
  16. the MethodInvocation class directly implements. So consider a PersonManager
  17. interface, a PersonManagerImpl class that implements it, and a definition of
  18. PersonManager.findAll=ROLE_FOO. In this example, any query for either
  19. PersonManager.findAll OR PersonManagerImpl.findAll will return ROLE_FOO.
  20. As we have always encouraged definition against the interface names (as per
  21. this example), this change should not adversely impact users. This change
  22. was necessary because of the new MethodDefinitionSourceAdvisor (see below).
  23. Refer to the MethodDefinitionMap JavaDocs for further clarification.</li>
  24. <li>MethodDefinitionSourceAdvisor can now be used instead of defining proxies
  25. for secure business objects. The advisor is fully compatible with both
  26. MethodDefinitionMap and MethodDefinitionAttributes. Using an advisor allows
  27. caching of which methods the MethodSecurityInterceptor should handle, thus
  28. providing a performance benefit as MethodSecurityInterceptor is not called
  29. for public (non-secure) objects. It also simplifies configuration.</li>
  30. <li>MethodSecurityInterceptor has moved from
  31. net.sf.acegisecurity.intercept.method.MethodSecurityInterceptor to
  32. net.sf.acegisecurity.intercept.method.aopalliance.MethodSecurityInterceptor.
  33. A simple find and replace will suffice to update your application contexts.</li>
  34. <li>All of the EH-CACHE cache implementations provided with Acegi Security have
  35. now been refactored to use a net.sf.ehcache.Cache obtained from
  36. EhCacheManagerFactoryBean, which is included with Spring 1.1.1 and above.
  37. See http://opensource.atlassian.com/confluence/spring/display/DISC/Caching+the+result+of+methods+using+Spring+and+EHCache
  38. for more about this bean, or the Contacts sample application for how to
  39. configure the EH-CACHE implementations provided with Acegi Security.
  40. Note the "cache" property is now required, and the old internally-managed
  41. cache properties have been removed.</li>
  42. </ul>
  43. </body>
  44. </html>