Start of 1.0.0 upgrade instructions.

This commit is contained in:
Ben Alex 2005-11-26 06:21:05 +00:00
parent 1593ac23da
commit e6ee8342c8
2 changed files with 34 additions and 0 deletions

View File

@ -41,6 +41,7 @@
<item name="External Web Articles" href="articles.html"/> <item name="External Web Articles" href="articles.html"/>
<item name="Products using Acegi" href="powering.html"/> <item name="Products using Acegi" href="powering.html"/>
<item name="Use without Spring" href="standalone.html"/> <item name="Use without Spring" href="standalone.html"/>
<item name="Upgrading to 1.0.0" href="upgrade/upgrade-090-100.html"/>
<item name="Upgrading to 0.9.0" href="upgrade/upgrade-080-090.html"/> <item name="Upgrading to 0.9.0" href="upgrade/upgrade-080-090.html"/>
<item name="Upgrading to 0.8.0" href="upgrade/upgrade-070-080.html"/> <item name="Upgrading to 0.8.0" href="upgrade/upgrade-070-080.html"/>
<item name="Upgrading to 0.7.0" href="upgrade/upgrade-06-070.html"/> <item name="Upgrading to 0.7.0" href="upgrade/upgrade-06-070.html"/>

View File

@ -0,0 +1,33 @@
<html>
<head>
<title>Acegi Security - Upgrading from version 0.8.0 to 1.0.0</title>
</head>
<body>
<h1>Upgrading from 0.9.0 to 1.0.0</h1>
<p>
The following should help most casual users of the project update their
applications:
<ul>
<li>The top level package name has changed. Simply find "net.sf.acegisecurity" and replace with
"org.acegisecurity".</li>
<li>net.sf.acegisecurity.providers.dao.AuthenticationDao is now org.acegisecurity.userdetails.UserDetailsService.
The interface signature has not changed. Similarly, User and UserDetails have moved into the latter's package as well.
If you've implemented your own AuthenticationDao, you'll need to change the class it's implementing and quite likely
the import packages for User and UserDetails.</li>
<li>Acegi Security is now localised. In net.sf.acegisecurity you will find a messages.properties. It is
suggested to register this in your application context, perhaps using ReloadableResourceBundleMessageSource.
If you do not do this, the default messages included in the source code will be used so this change is
not critical. The Spring LocaleContextHolder class is used to determine the locale of messages included in
exceptions. At present only the default messages.properties is included (which is in English). If
you localise this file to another language, please consider attaching it to a
<a href="http://opensource2.atlassian.com/projects/spring/secure/BrowseProject.jspa?id=10040">new JIRA task</a>
so that we can include it in future Acegi Security releases.</li>
</ul>
</body>
</html>