How automatic dirty checking works for persistance layer?

Question

Hi,
I recently started learning about Java Persistance API and also about Hibernate and I came across this example
private void addPersonToEvent(Long personId, Long eventId) {
    Session session = HibernateUtil.getSessionFactory().getCurrentSession();
    session.beginTransaction();
    Person aPerson = (Person) session.load(Person.class, personId);
    Event anEvent = (Event) session.load(Event.class, eventId);
    aPerson.getEvents().add(anEvent);
    session.getTransaction().commit();
}and in the explanation they have given like
After loading a Person and an Event, simply modify the collection using the normal collection methods. As you can see, there is no explicit call to update() or save(), Hibernate automatically detects that the collection has been modified and needs to be updated. This is called automatic dirty checking, and you can also try it by modifying the name or the date property of any of your objects.
How does it work? I know that something called dynamic proxy that exist in java, is it by that?
Let us say I want something to do like an interceptor, whenever I call a particular method on an object, that call will first be address by me and then it will be delegated to the actual object.
Say
public void handleEvent(SyncCompletedEvent event)
        // We have to handle this one, this is the only one that will trigger the start up sync
        // however, this request doesn't need response!
        if (event.isSenderDeviceCommunicator())
            // set the request to null, so that no intermediate response will be sent out.
            handleRequest((UpmSyncRequest) null);
        if(event.getSubType().equals(SyncCompletedEvent.SUBTYPE.LEGACY_SERVER_STARTUP_COMPLETED))
            ((UpmService) getService()).scheduleAuditBackup(false);
    }

Answer 1

What kind of problems do you have with the Firefox 28 release?
Did you check your security software (firewall, anti-virus) to make sure that the new version in allowed?
It is possible that your security software (firewall, anti-virus) blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full, unrestricted, access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.org/kb/Server+not+found
*https://support.mozilla.org/kb/Firewalls
*https://support.mozilla.org/kb/fix-problems-connecting-websites-after-updating
You can create a new profile as a test to check if your current profile is causing the problem.
See "Creating a profile":
*https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox