This is mostly because i am up to my head with new projects, BPM, SOA, BI and other fusion middleware technologies. Also because:
By default when you type a value in an input list of values the query is executed always with the LIKE operator.
This is very annoying for users that do heads-down data entry.
Also if the field is a number executed query force full table scan causing performance issues.
We just need the option to disable auto-suggest behavior (on design time) so that the query is executed with '=' operator and the LOV does not open when the value entered is valid.
This issue was found by my colleague and friend Gabriel Sideras that was assigned the task to create web services from our business components.
He noticed that sometimes the entity validations was not executed from the web service. This happens when the entity primary key has checked the attribute refresh after insert.
This is reproduced at the attached test case that a simple createDepartment web service is created with HR department entity and view.
There are about 400 application roles defined in our application.
In a production environment there are about 1000 users that have groups of these roles so there are about 7000 role assignments.
We the policy store to be Database based for production environment (as it is recommended by documentation) in order to support clustering Weblogic environment.
Then the hole performance of Enterprise Manager was much worse than in file based. It took about 8 minutes to query the roles. This was happening also in every action , create, assign, remove role.