Combo box does not remember values in table

When you define a List of Values in a View object as Combo Box with List Of Values there is an option to define ‘Most Recently Used Count’

Where you, enter the number of items to display in the choice list when you want to provide a shortcut to the end user to display their most recent selections.


This is quite useful functionality and it work fine when the field is used in a panel form layout.

Yet when it is used in table then it does not work, no matter how many times you select a value it does not remember the previously added values.

Is this a bug?

Test case:
http://adfbugs.googlecode.com/files/TestComboBox.zip

Still reproduce in jdeveloper 11.1.2

SR 3-3705906727 was posted for this.
Enchancement request that was created was rejected by Oracle development team.

=== ODM Answer ===

The MRUCount when the inputComboboxListOfValues is in a table won't work when ADF bindings are used:

The LOV bindings are created dynamically when used in a table and the "Most Recently Used Count" (MRU) feature is not enabled then.
MRU doesn't work in af:query too.

There is currently no plan to implement this feature in future releases.

Jdeveloper 11.1.1.5 severe bug (Fixed in 11.1.2)

We started evaluating jdeveloper 11.1.1.5 in order to see if and when we will use it.
When you press rollback and the page has a table with editable fields, all fields get the same values as the last row of the table.This is a really blocking issue in order to use the latest version
It seems the problem is in the immediate property of Rollback button

This is also in forums
http://forums.oracle.com/forums/thread.jspa?messageID=9587923#9587923

Oracle have logged a bug 12551764 for it and an Alert in support
Note 1321896.1 - 11.1.1.5.0 Regression: Rollback Button With Property immediate="true" Causes Replacing Existing Rows With Current One
since it is possibly going to affect all users of 11.1.1.5
Oracle is working on a patch for it.
I will do more investigation about the posted bugs here when this patch is ready

Application Module cannot get principal when you use transaction controller in task flows (Fixed in 11.1.2)

When you use Transaction behavior in Task flows then ApplicationModuleImpl.getUserPrincipalName gives a java.lang.NullPointerException
To reproduce it I have an application module with an exposed method:

public void checkTransaction(){
System.out.println(this.getDBTransaction().getSession().getEnvironment().get("jbo.user.principal"));
System.out.println(this.getUserPrincipalName());
}

I also have 2 ‘isolated’ task flows, StartNewTransaction with ‘Always Begin new Transaction’ and UseExistingTransaction with ‘Use existing transaction if possible’




I have user: ‘user1/welcome1’ and run TestTransactions page and loggin.
In main page checkTransactions works as expected. Yet in other task flows it gives a:

java.lang.NullPointerException
at oracle.jbo.server.ApplicationModuleImpl.getUserPrincipalName(ApplicationModuleImpl.java:8429)
at model.modules.AppModuleImpl.checkTransaction(AppModuleImpl.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
…

Is this a specific method bug?
Will I have issues with history columns?
Do I loose any other security context?

Test Case:
http://adfbugs.googlecode.com/files/testTransactions.zip

Does not reproduce in jdeveloper 11.1.2