To resolve my problem I have added a new attribute; nullValueKeyCol to the
result element.
This attribute tells iBatis to check for a value in the column referenced in
nullValueKeyCol and if it has a non null value it sets the property to the
null value.
An example may clarify this better.
Just curious what the best practices about this are. And since the
DaoExcpetion is now a runtime you have to explicitly put your try {}
catch {} blocks somewhere right :)
Here is my setup
Struts Actions (Presentation)
Service Layer (Business Logic) I assume here :)
Dao layer (Data Access
In Struts I would catch the action where it happens and keep
rethrowing it to the container.
This way web.xml error page can display a nicley formated message.
.V
Nathan Maves wrote:
Just curious what the best practices about this are. And since the
DaoExcpetion is now a runtime you have
I only catch exception if i need to clean something up or if i can
recover from it. Otherwise, let em rip. Between my Presentation layer
and my service layer i throw RuntimeExceptions. I do logging of
exceptions at the highest point of my application. If i wanted to
provide a pretty screen for
4 matches
Mail list logo
