New work rhythm is faster, so not too much update blog. Recently, Ibaits code conventions and JUnit best practice have been written, and I'm glad that the community can progress along the path of agility and TDD. Friends who need these two things can send mail to me.
Acegi out 0.8, the changes are really quite a lot, the original 0.7 of the application, changed one hours to completely upgrade successfully. Memo:
1 The most intimate change is that the filter chains can be loaded in a spring container and no longer has to be declared in the Web.xml as a long string of filter. For example:
<bean id= "Filterchainproxy" class= "Net.sf.acegisecurity.util.FilterChainProxy" > <property name= " Filterinvocationdefinitionsource "> <value> convert_url_to_lowercase_before_comparison PA Ttern_type_apache_ant/**=httpsessioncontextintegrationfilter,authenticationprocessingfilter,...... ;/value> </property> </bean>
2 httpsessionintegrationfilter have disappeared, using net.sf.acegisecurity.context.HttpSessionContextIntegrationFilter instead, such as: <bean id= "Httpsessioncontextintegrationfilter" class= " Net.sf.acegisecurity.context.HttpSessionContextIntegrationFilter "> <property name=" Context "><value >net.sf.acegisecurity.context.security.SecureContextImpl</value></property> </bean>
This "context" property has to be set yo.
3 added a feature that allows you to declare a Httpsessioneventpublisher context listener in Web.xml, and think about spring's now immature message publishing mechanism (AOP), which is used primarily for journaling. I'm not used to this function for the time being.
Conclusion: Acegi is very strong, but also very annoying, this time 0.1 upgrade let me toss for one hours, hey.
