Yes, I have been through that document and done everything except the primary key generation. Our db's do use the Identity/Sequence features for generating primary keys and this cannot be changed due to legacy systems that also access the db. The error I see against SQLServer when performing a Commit after a CreateInsert, Update, or Delete is this:
<LifecycleImpl> <_handleException> ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase INVOKE_APPLICATION 5
javax.faces.el.EvaluationException: oracle.jbo.JboException: [oracle.jbo.DMLException: JBO-26080: Error while selecting entity for GetValueRuleEO]
This happens against multiple entity objects. The entity PK's are defined as oracle.jbo.Domain.DBSequence with Updatable as Never and no Refresh. Is there a way to set the properties of the application model at runtime, possibly within the initialization servlet?
I set my debug level to FINEST and this line happens prior to the exception above:
<SQLServerException> <logException> *** SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR. Msg 1003, Level 15, State 2, Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR.
Googling this I found this link in the forum: ADF and MSSQL 2005 problems -> FOR UPDATE clause allowed only for DECLARE C
My entities were created with SQL92 and Java. There is no answer to how he made out.
So I think I the app is still trying to run against an Oracle db since the "for update" is Oracle related. My driver class is com.microsoft.sqlserver.jdbc.SQLServerDriver and the library is Sqljdbc4.jar.
Any ideas are welcome!