see... the thing is, evaluating against a '0' for numeric ... or a '0000-00000 ... etc...' for UUID is easy... (unless you actually want it to return valid records with these values!) ... because the likelyhood of me requesting an ID or UUID with the value of '0' is pretty slim. but in my case when i'm trying to build a 'getByAttributes', passing in 'false' is legitimate for searching a boolean field, and it's a rather frequent case... unlike '0' for numeric on a straight up get(). so, i can't really check against the potential for default population of 'false'... when 'false' is a likely candidate for an attribute passed into the request, and i can't either evaluate for 'true and false', because the boolean type restriction only allows 'true or false' as an option.
i'm really wanting to pass transfer objects cleanly between my handlers and managers... the only other option that i can think of besides changing all my booleans to strings is breaking my attributes out of the transfer objects and passing them directly into the manager from the handlers. yuck. -- Jim Rising Serial Entrepreneur Software Engineer Web Developer "Knowledge work requires both autonomy and accountability." --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
