Hi! > what would be the representation used for a date/long/double in a > string? Can we look into the xsd definition for that? Would an xsd > type representation converter be a good solution for this? > No need to do anything special other then fixate the locale/encoding used (configureable through context-param) when encoding the values. The same way as it is if JSF converts a value to string and back.
See if there is a converter attached/if not lookup by type/if not fallback to serialization ... sounds familiar, no? ;-) It already works, JSF converts to a date and back from user input. This is why I dont see any difference between user input and url paramter. We can fully rely on JSF default mechanism - and the user has the full, well known configuration possibillities. Ciao, Mario
