G
Guest
I was wondering other opinions on this topic... I am working on an n-tier
application which may be broken out to different servers at a later date.
How should I go about the validation? I would like to assume that the UI
later will handle a lot of this but I cannot be 100% set on this as another
developer may not expose all the validation rules if they make a new front
end. Right now my data access layer uses checks within the procedures as
well as constraints and foriegn keys. This however again doesn't make my
data 100% but helps a great deal. I was thinking about having a custom
exception in my BLL named ValidationException in which I can do all checks
there. This way when users screw up on entry I can catch this in the UI to
display a friendly error message instead of passing it to my exception
handler. I would still do client side validation as well to cut down on the
exceptions thrown. What are your thoughts on this method and is this quite
common in n-tier applications where there may be multiple developers working
on different UIs?
application which may be broken out to different servers at a later date.
How should I go about the validation? I would like to assume that the UI
later will handle a lot of this but I cannot be 100% set on this as another
developer may not expose all the validation rules if they make a new front
end. Right now my data access layer uses checks within the procedures as
well as constraints and foriegn keys. This however again doesn't make my
data 100% but helps a great deal. I was thinking about having a custom
exception in my BLL named ValidationException in which I can do all checks
there. This way when users screw up on entry I can catch this in the UI to
display a friendly error message instead of passing it to my exception
handler. I would still do client side validation as well to cut down on the
exceptions thrown. What are your thoughts on this method and is this quite
common in n-tier applications where there may be multiple developers working
on different UIs?