Correct synchronization issue with FilterToBeanProxy initialization (thanks to George Franciscus and Volker Malzahn as per acegisecurity-developer discussion 4 June 2005).
This commit is contained in:
parent
1cfdc86ff4
commit
a7b5299e77
|
@ -150,7 +150,12 @@ public class FilterToBeanProxy implements Filter {
|
||||||
.getServletContext());
|
.getServletContext());
|
||||||
}
|
}
|
||||||
|
|
||||||
private void doInit() throws ServletException {
|
private synchronized void doInit() throws ServletException {
|
||||||
|
if (initialized) {
|
||||||
|
// already initialized, so don't re-initialize
|
||||||
|
return;
|
||||||
|
}
|
||||||
|
|
||||||
initialized = true;
|
initialized = true;
|
||||||
|
|
||||||
String targetBean = filterConfig.getInitParameter("targetBean");
|
String targetBean = filterConfig.getInitParameter("targetBean");
|
||||||
|
|
|
@ -36,6 +36,7 @@
|
||||||
<action dev="benalex" type="fix">AbstractAuthenticationToken.getName() now returns username alone if UserDetails present</action>
|
<action dev="benalex" type="fix">AbstractAuthenticationToken.getName() now returns username alone if UserDetails present</action>
|
||||||
<action dev="raykrueger" type="update">AuthorityGranter.grant now returns a java.util.Set of role names, instead of a single role name</action>
|
<action dev="raykrueger" type="update">AuthorityGranter.grant now returns a java.util.Set of role names, instead of a single role name</action>
|
||||||
<action dev="benalex" type="update">JavaDoc improvements</action>
|
<action dev="benalex" type="update">JavaDoc improvements</action>
|
||||||
|
<action dev="benalex" type="fix">Correct synchronization issue with FilterToBeanProxy initialization</action>
|
||||||
</release>
|
</release>
|
||||||
<release version="0.8.2" date="2005-04-20">
|
<release version="0.8.2" date="2005-04-20">
|
||||||
<action dev="benalex" type="fix">Correct location of AuthenticationSimpleHttpInvokerRequestExecutor in clientContext.xml</action>
|
<action dev="benalex" type="fix">Correct location of AuthenticationSimpleHttpInvokerRequestExecutor in clientContext.xml</action>
|
||||||
|
|
Loading…
Reference in New Issue