[Springframework-developer] Spring 1.2 RC2 and Acegi Security

[Juergen H. <ju...@in...>]

Hi Ben,

as Matt has noticed, there is a change in Spring 1.2 RC2 that breaks Acegi
Security:

<matt>
It's cool to see that the Spring Team has released 1.2 RC2, but there's a
change that causes Acegi Security (v0.8.1) to fail.

• refactored static PathMatcher class into PathMatcher interface and
AntPathMatcher implementation

This change seems to cause this issue with Acegi Security. Right now, I have
Spring 1.2 RC1 and Hibernate 3.0.1 bundled into AppFuse 1.8. I was hoping to
upgrade to Spring 1.2 RC2, but it doesn't look like this will work - unless
the Acegi Team releases a new version that supports 1.2 RC2 (hint, hint ;-).
</matt>

I've refactored the static PathMatcher into a PathMatcher interface and
AntPathMatcher implementation class, after repeated questions in that
respect. I must admit I haven't really considered that other *libraries*
might access that code, just that users might.

Hence, I've accepted the tradeoff of backwards-incompatibility for 1.2,
because it's easy enough for users to migrate affected code - and the
utilities in Spring's util package are considered somewhat for internal use
in the first place. But unfortunately, there's the issue of collaborating
libraries...

Anyway, I would like to keep the refactored PathMatcher, so I'd like to
encourage you to release an Acegi update release (0.8.2?) at your earliest
convenience, ideally alongside Spring 1.2 final (in about two weeks) or
earlier. Users should have a fully working combo then again.

Sorry for the inconveniences caused,

Juergen