Hi everyone,
Is anyone using iBatis with ATLAS or other AJAX technologies? In our
current project, under .Net 2.0, I'm using ATLAS on the front-end to do
in-place editing.
I'm using an architecture similar to that of the NPetShop application -
Web, Presentation, Service and Persistence, plus a Domain. I've also
broken my pages down into user controls which are passed domain objects
to show/return. When a change is made to a field, it raises an event
which then bubbles up (maybe through a couple of user controls) to the
parent page. The parent page contains the main object, which is then
saved to the database.
For example, I have a Drive which contains an Appointment which contains
a Location. When I change the street address it of the Location, it
raises an event in Location, which raises an event in Appointment, which
raises and event in Drive. Drive then persists itself to the database
via the other layers.
The problem is that while I'm saving the entire Drive object (which also
contains other objects, not just those I mentioned) to the database
only 1 field has changed. So every time a user updates a field, I save
a lot of data that hasn't changed.
I don't want persistence details in my front-end, so I don't want the
changed field to know which database field it corresponds to.
Has anyone done this or have any suggestions about what to do?
Thanks,
Brian
