Bindings problem after migration to 11g

Question

I recently migrated my 10.1.3.4 adf/bc app to 11.1.1.1.0. I've managed to work out most of the migration issues/bugs, but there is one I don't understand. In one of the backing beans, I have code to check if the transaction is dirty. This code is executed when the user clicks the button on the associated page. In the 10.1.3.4 version, I was getting the right answer as far as checking to see if the transaction was dirty, now i am not. Basically, I'm evaluating the value of ("#{bindings.Commit.enabled}" to determine if trans is dirty. here is the code from the backing bean:
public String checkDirty(){
Boolean b;
if (bindings == null){
System.out.println("null bindings");
b = ((Boolean) JSFUtils.resolveExpression("#{bindings.Commit.enabled}"));
// if there is no commit binding, the form is by definition not dirty
if (b == null){
System.out.println("didn't find commit binding");
System.out.println("value is: " + b.booleanValue());
return null;
The line b = ((Boolean) JSFUtils.resolveExpression("#{bindings.Commit.enabled}")); is now returning false, when it should be returning true. Does anyone know why?

Answer 1

Hi,
Did you have any uncommitted changes when you invoked checkDirty method, if not what you have observed is correct and what is the status of commit button in the ui, is it enbaled or disabled?
If you feel still it is not behaving correctly, you can try calling getDBTransaction().isDirty() method which returns true if the transaction is dirty, See [this post|http://forums.oracle.com/forums/thread.jspa?messageID=3641722&#3641722] for more details.
Sireesha