we will have mutliple forms and update methods.
returning a string-value containing the error if any has occured is bad
cause the error-message would be hardcoded into the application.
error-messages must be:
multi-language (=> must be linked into a language field)
should be template (=> cause you have to replace sometimes the arguments of
an error message to make it usefull... for example:
*the name "swagner" has already been taken* instead of *the name has
already been taken*
To make it running there must be templates stored into the database which
must be loaded through "velocity" and replaced with arguments and then
returned to the client.
missing methods:
getErrorById()
It should return an error-Object with an header and a message (maybe
possibility to resume)
Original issue reported on code.google.com by seba.wag...@gmail.com on 14 Apr 2007 at 8:44
Original issue reported on code.google.com by
seba.wag...@gmail.com
on 14 Apr 2007 at 8:44