Consider the following SQL Server view...
create view Employee_DOC
GenderDesc = dbo.getCodeDescriprtion( 'GENDER', GenderCode ),
It uses a derived column and is thus unupdateable (no insert or update). It can not be used by an Entity bean if you want that bean to be updateable. What would be great is if you could specify a table (or view) to used for reading and a different table for saving. This does not appear to be a feature of EBJ3/Hibernate, but is there a way to achieve the same outcome?
Amazing product!! My deepest admiration to those responsible.