To add to what Thomas said, if you use EntityManager#find(Class
entityClass, Object primaryKey), and the entity already exists in the
current persistence context, your JPA implementation will not hit the db
again (check the javadoc in javax.persistence.EntityManager). So, if you
then use request sc
First, this has nothing to do with the Editor framework, but with
RequestFactory.
If you're not using a Locator, or you're not overriding the isLive() method
of your Locator, then this is the expected behavior: this is how
RequestFactory determines whether an entity is still "alive" before send
During update the entity with Editor framework select from db calls twice.
May be it's not a problem but a feature of Editor framework?
Here is a code snippet:
public class UserActivity extends BasicActivity {
...
interface Driver extends RequestFactoryEditorDriver {
}
private UserProxy use
