A DTO is a Data Transfer Object. Google it for more discussion (Martin Fowler probably has some stuff to say about it). The idea is a small simple object (only getters and setters) that brings only...
Type: Posts; User: jasonmp85; Keyword(s):
A DTO is a Data Transfer Object. Google it for more discussion (Martin Fowler probably has some stuff to say about it). The idea is a small simple object (only getters and setters) that brings only...
I'm not sure what you mean by "generic verification". The generic DAO patterns I've seen are all based around the fact that all DAOs do pretty much the same stuff. You make all the DAO interfaces,...
Yes, I think that is the correct way to do it. Also note that within a <form:whatever> tag, the c:if conditional will work. As I understand it, you have to be within a binding context for the errors...
During form validation, I'd like to be able to show errors in two places:
1. In a list at the top of the form, with all errors listed.
2. At each field.
Listing them at each field is clear:...
Sounds promising, but semantically I'm not sure I can come to terms with this (using a wizard controller to allow multiple forms per page)? I'm sorry if I come across as picky here, but I am just...
Ok, so I hate to reply to my own post again, but here goes.
How do I cleanly validate this aggregate form? I don't care what they entered in the "addState" box if they submitted the "addCountry"...
I suppose my recourse is to create one aggregate FBO with enough information for both possible branches and have different values for the two submit buttons.
The controller would decide to do...
I think that's unnecessarily complicated. If at a later date I wanted to again separate these two forms, it would be easier to already have the logic separated.
I feel this should be possible and...
I'm working on a webapp with a bunch of administrative forms for adding things that appear as finite enumerations on the rest of the website (for instance, the administrators are allowed to add...
Just thought of a related question.
In the first case above, validators could be written to test the form-backing object for completeness: is every field there, are phone numbers really phone...
This is pretty much exactly what I was looking for. I have a decent bit of domain logic, so I think implementing some other form backing object to transfer user-entered data back and forth isn't a...
I'm deep in my first Spring/Hibernate project and have a question regarding domain object design.
I first designed our datamodel, wrote the hibernate mappings, and then built a businesslogic front...