Probably like many here, I have been using my @Entity class objects as form backing objects as well as for database access.
Now I want to add a member to an @Entity class that represents a checkbox in the form. From what I have observed so far, Spring 3 MVC will attempt to map every member of an @Entity class to a database column inside the database table that the class represents. I do not want the new class member (that represents the checkbox) to be mapped to a column - it's just a flag for business logic.
How I do I accomplish this without wrapping the entire @Entity class in a new class (for a form backing object) that has one more member (the boolean)?


Reply With Quote
