[ http://jira.magnolia.info/browse/MAGNOLIA-1957?page=all ]
Grégory Joseph resolved MAGNOLIA-1957.
--------------------------------------
Resolution: Fixed
fixed - the only real "hack" was in JCRAuthenticationModule, where we still
want to throw the specific jaas exception if possible (if we're on java5) so
that we can let the user know more precisely why the login failed.
> Some superfluous usages java5 API
> ---------------------------------
>
> Key: MAGNOLIA-1957
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1957
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5
> Reporter: Grégory Joseph
> Assigned To: Grégory Joseph
> Priority: Critical
> Fix For: 3.5.1
>
>
> SystemContextImpl (ThreadLocal.remove())
> CheckAndUpdateExistingFilters (Long.valueOf())
> ModuleBootstrapTask (String.contains())
> ModuleDependencyBootstrapTask (String.contains())
> JCRAuthenticationModule (AccountNotFoundException and AccountLockedException)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
