many fields. i cant think a better way to make this less painful.
ex, class pipe has an int id, float len, float diameter, enum type, area, gas and about 30 fields more. classs artifact has about 60 fields
is there a better way to get every field from the form, validate and sending it to a database without do it field by field?
i was thinking in a array of fields, but not all field has the same type
Felipe, a class with many fields deserves a better look: Is it necessary such a number of fields ??? You can refactor out with more classes, maybe base class(es) using inharitance. With respect to validation, you can use, among others, Bean Validation: https://beanvalidation.org/
Absolutely agree with @R_r_F_BR . Some more thoughts from me: If those classes with 60 field are actually entities and correspond to DB tables with 60 columns, then your may consider using embedded entities to keep your DB tables but touch only entity classes. However, entity classes with many fields are not so bad. They just reflect data model. I don't see a big problem there unless some of those fields conform sets that represent another logical entity. Especially, if such logical entity is reusable. But even though, it may be done intentionally, denormalized for performance sake.
If you're using spring, validation: https://docs.spring.io/spring/docs/4.1.x/spring-framework-reference/html/validation.html
Обсуждают сегодня