Changeset 2285

Show
Ignore:
Timestamp:
01/19/08 17:07:03 (12 months ago)
Author:
david
Message:

Info about deprecated stuff

Location:
trunk
Files:
2 modified

Legend:

Unmodified
Added
Removed
  • trunk/RELEASE_NOTES

    r2269 r2285  
    66 
    77The following is a brief summary of the most important changes in this release. For a full list of new features, changes and bugfixes, please refer to the CHANGELOG. 
     8 
     9Also, please pay special attention to the list of deprecated elements at the end of this description. 
    810 
    911ATTENTION: Some bugfixes caused changes to internal behavior. Make absolutely sure that your application is ready for an upgrade to 1.0 by reading the UPGRADING document. 
     
    1214-------- 
    1315The check against isSecure() is now performed in the Security Filter, which always runs unconditionally when core.use_security is enabled. This is a bug fix that was made because it would otherwise be impossible to make certain changes to Agavi's authentication model. 
     16 
     17Deprecated elements 
     18------------------- 
     19- The "core.use_routing" configuration directive is now deprecated. Instead, please use <parameter name="enabled"> in factories.xml's <routing> element to control the use of routing on a per-context basis (this is a new feature). 
     20Existing "core.use_routing" directives will be used as a fallback until the directive is removed completely in Agavi 1.1 
     21 
     22- AgaviSecureWebRequest has been deprecated. There is no replacement available. It will be removed in Agavi 1.1, but of course, you can continue to use the implementation from an older release. 
     23 
     24- AgaviAdodbDatabase has been deprecated. There is no replacement available. It will be removed in Agavi 1.1, but of course, you can continue to use the implementation from an older release. 
     25 
     26- Validation severity "none" is now called "silent". 
    1427 
    1528 
  • trunk/UPGRADING

    r2269 r2285  
    66 
    77Upgrading to Agavi 1.0 requires very little effort as the API remained identical. 
     8 
     9It is recommended that you refer to the RELEASE_NOTES to see a list of deprecated elements, and change your application accordingly. 
    810 
    911However, two areas might affect your application: