Continue Acegi -> 0.8

The new work is rapid, so I don't update my blog. I have recently prepared IBaits Code Conventions and JUnit Best Practice, and I am very happy that the group can progress according to the road of agility and TDD. Friends who need these two stuff can send me.

Acegi has been 0.8, the change is really a lot, the original 0.7 application, has changed for more than a month to completely upgrade success. Memo:

1 The most intimate change is that Filter Chains can be loaded in the Spring container, and no longer have to declare a long string Filter in Web.xml. E.g:

CONVERT_URL_TO_LOWERCASE_BEFORE_COMPARISON PATTERN_TYPE_APACHE_ANT / ** = httpSessionContextIntegrationFilter, authenticationProcessingFilter, ......

2 HttpSessionIntegrationFilter has disappeared, net.sf.acegisecurity.context.HttpSessionContextIntegrationFilter used instead, such as: net.sf.acegisecurity.context.security.secureContextImpl

This "context" attribute is not allowed.

3 Add a feature, you can declare an HttpSessionEventPublisher Context Listener in Web.xml, think about Spring is still not very mature message publishing mechanism (AOP), mainly for logs. I haven't used this feature yet.

Conclusion: Acegi is very strong, but it is also very annoying, this time the upgrade of this time makes me toss for more than an hour, oh.