(http://jira.theresis.thales:8180/browse/AUTHZFORCE-41) fixed. Tests
needs to be made to ensure that doesn't happen again
Essentially the bug was made by a Content in the attribute that wasn't
set. The old scheme were used but nothing were updated in the new. So
attributes DateTimeAttribute and TimeAttribute could'nt be used by the
functions associated with these attributes.
This sort of stuff needs to be taking care of in the others "exotics"
attributes (not string attribute actually...). In the same way all the
functions needs to be checked so that they really use the new scheme
(oasis-xacml-model) and not the old SunXACML shaky scheme