Is there a path for data validation in an elegant, standard, and concise way? Is there a way that doesn't fall into unreadability, helps us to keep most of the data validation logic together, and has most of the code already done for us by developers of popular Java frameworks?įor us, developers of the CUBA Platform, it is very important to let our users follow the best practices. So, after a while, when the project grew up enough, it became quite hard and expensive to keep these validations consistent and following requirements, which, as I've said, are often fuzzy. This code was full of if-else statements, throwing different unchecked exceptions, and making it hard to find a place where data could be validated. So, data validation code could be found everywhere - in Javascript snippets, Java screen controllers, business logic beans, domain model entities, database constraints, and triggers. Their teams worked under the great pressure of deadlines, unclear requirements, and just didn't have enough time to make validation in a proper and consistent way. Often, I have seen projects that didn't appear to have any conscious strategy for data validation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |