If you do your work inside a conversation, and use an extended persistence context in an SFSB, or a seam-managed extended persistence context, then the entity bean will remain in the managed state for the entire conversation and will be automatically flushed to the database.
Well,it does just not work.
I have current user entity bean in conversational context and all
it`s properties are bound to input components as follows:
When I change the firstname property, next time page is rendered the firstname is changed. Also seam debug page shows that bean 'current' is changed.
But database table row mapped to this entity bean does not change.
Or are they flushed after conversation end?
not flush,but the value binding to the component was changed if you submit the form