clarencen/lshift — Issue #255: Attribute type should be appropriately formatted
Author: clarencen
Created: 2011-11-14 22:42:16+00:00
State: open

#199 fixed an issue where the DateCategoryFunction could not parse a yyyy-MM-dd date. However, the side effect of this is that when the agent generates subsequent constraints for further querying, it does so using the date type, which, in turn uses the default serialization of that class, i.e. a string with a complete ISO date including seconds and timezone. When this is sent back to the participant, it is legitimately expecting a date string in the format it sent originally sent out.

Hence we need a mechanism that honours the formatting/implicit type that the participant understands - this should probably be configurable together with the data type of the category.