ADF BUGS FACTS & Workarounds

Access Keys are accessible even from a modal popup

2011-12-20T01:33:00.000-08:00

When a popup is open in a page in default (modal) mode then the rest of the components of the page are not accessible with mouse, yet if buttons have Access keys they are still functional allowing the user to brake the functionality.

n the attached test case run testpopup page
Press Edit button to open popup
Press Alt+Shift+c access key of Commit button

Expected: Nothing should happen
Actual: Commit is performed and popup is closed.

Test case.

SR is posted for this and Bug 13338347: ACCESS KEYS SHOLD BE DISABLED BASED ON THE CONTEXT

Yet the Oracle development consider this as a Browser issue. 'The issue is not in the scope of the ADF Product as this is the feature of the browser. '

We are working on a workaround about this issue.
We are based on the fact that when a button is disabled then the access key is not functional.
So on popup FetchListeners we disable the buttons of the main page and on popupCancelListeners we enable buttons again.
It seems to work, yet we need to check any side effect and we need to implement it for all popups.

Pressing 'Tab' in LOV field new bug in jdeveloper 11.1.2.1

2011-10-06T00:10:00.000-07:00

Trying to evaluate latest version of jdeveloper 11.1.2.1 in order to migrate our applications that is still in 11.1.1.4 i hit on the following bug.

While navigating through panel form fields with tab key, all validations of the page are thrown as if a full submit was performed.
This happens when you have input list of value field and the focus is on the field and you press tab key. The input list of value is autosubmit in order to refresh other fields

In the test case run testTab page and press CreateInsert button. Click on Department or Job List of value field and press Tab key. All validations of the page appear.
I also notice that errors appear in Greek even though my browser language is in English.

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

Bug 11939353 was already logged in oracle support which is fixed in a future release.

also in OTN Thread: Validation issue
https://forums.oracle.com/forums/thread.jspa?threadID=2254388&start=15&tstart=0

According to this thread a workaround exist in Didier's blog:
How To Avoid The JBO-27014 Error During The AutoSubmit

Cannot use a region in a page more than one time?

2011-08-28T02:49:00.000-07:00

In our application we use regions for reusability and consistency.
For example we have An address region that we reuse in order to show and edit a person address and a company address. We pass the address owner as a parameter to the region in order to show corresponding data.

Yet if regions are placed in the same page then both regions show the same data even if they get different parameters.

This is because of automatic application modules nesting.
The framework see that AddressModule is already in data control and it use the same for both regions due to shared data control scope.

It does not happen if we don't use shared data control scope, yet then we have a different database connection for each region. It does not seems right to have different connection to get different data!!?

In the test case i have a simple Department Task flow that query for specific department depending on passed parameter inDepId

Then in a page i place the same region 2 times with different parameter passed in each region.
Yet when i run the application both regions show the same data.

Is there a way to show different data without having different database connection?

Test Case:

http://adfbugs.googlecode.com/files/TestRegions.rar

Rollback is executed when a region is refreshed

2011-08-16T06:10:00.000-07:00

We are using Task flows as regions in jdeveloper 11.1.1.4 in the latest project.
I have just noticed that when a region refreshes then a data control transaction rollback is executed transparently.
This does not happen the first time the region is displayed but every time it is refreshed after that.
This cause unexpected behavior of loosing data and the current rows of any other shared transaction task flow.

Could this be an expected (designed) functionality? Why?

As a test case I have 2 application modules (DepartmentsModule and Employees module) and a page that has departments and a region that has Employees with ‘share transaction if possible’ in the EmployeesTaskFlow.
Also the EmployeesTaskFlow get as parameter the current DepartmentId and has Refresh condition ifNeeded so that it refresh every time I navigate into departments.

Yet when I press next button I loose any change made on current department and I stay in the same row.
What I see in log is that Rollback is executed as a consequence of region Refresh and releaseViewPort.

Is this expected behavior or a bug?

I will check also what happens in 11.1.2 that it seems the nesting implementation have changed:
http://one-size-doesnt-fit-all.blogspot.com/2011/08/task-flows-sayonara-auto-am-nesting-in.html

It reproduce also in 11.1.2

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

A Perfect explanation and solution is given by Oracle Support. I will put it as is here:
@ At the point when the customer decided the region should share the
@ transaction with its parent, he also made the region a potential actor on the
@ parent transaction. Since the transaction mode on the region is not 'Always
@ Use Existing Transaction', the region transaction is not necessarily created
@ by the parent (and I will come back to that later), the behavior of the
@ region becomes the behavior of the parent even if they don't share the same
@ datacontrol. That is because both datacontrol are in one transaction since
@ the transaction is shared. When the region refresh, it rollback the
@ transaction which rollback both datacontrol.
@ .
@ To make the share mode work, the main point the customer should pay attention
@ to is that the transaction should be created by the parent, not by the
@ region. If it is created by the region, then the region become the owner of
@ the transaction and will rollback when the region is refreshed. If the
@ transaction was created by the parent it will work as expected.
@ .
@ What you need to do is ensure that the transaction is owned by the parent.
@ You need to have it created before the region. They are several ways to do
@ that:
@ 1) Have the parent page in a bounded taskflow with 'Always Begin New
@ Transaction' mode on.
@ 2) Call beginTransaction() on the DataControlFrame in an action that
@ navigates to the parent page with the region.
@ 3) Have a method activity that executes beginTransaction() on a request bean
@ before navigating to the parent page with the region.
@ The code to do begin the transaction is:
@ .
@ public void beginTransaction()
@ {
@ BindingContext context = BindingContext.getCurrent();
@ .
@ String dcFrameName = context.getCurrentDataControlFrame();
@ DataControlFrame dcFrame = context.findDataControlFrame(dcFrameName);
@ dcFrame.beginTransaction(new TransactionProperties());
@ }
@ .
@ To prevent the region from owning the transaction and run into these types of
@ issue for share mode, you can set the transaction mode on the taskflow to:
@ or 'Always Use Existing Transaction' in the
@ property inspector. If the transaction does not exist, an exception is
@ thrown.
@ .
@ I modified the original test case to illustrate the different options. Open
@ the workspace and look at adfc-config.xml. Run the Start page, withoutTrans
@ is the original test case, withTrans and beginTrans are 2 options that work.
@ .

Resolution Test Case
http://adfbugs.googlecode.com/files/TestRegionRollback2.zip
Hello

Unfortunately it seems that the issue is not fully resolved.
This works until a Data control frame commit or Rollback is executed.
Then it seems that the parrent looses control again of the transaction and regions rollback again on every refresh...
In the test case i added 2 buttons that do :

DataControlFrame dcFrame = context.findDataControlFrame(dcFrameName);
dcFrame.commit();
and
DataControlFrame dcFrame = context.findDataControlFrame(dcFrameName);
dcFrame.rollback();

The test case work fine until any of the commit or rollback transaction is pressed
Then Next button still causes rollback to be executed.

This means that still i cannot control the full data control frame transaction when i have regions with parameters.

New test case
http://adfbugs.googlecode.com/files/TestRegionRollback3.zip

Table Filter Number format bug

2011-06-26T11:10:00.000-07:00

In a filterable table when we typed a number with decimals we got the following error:

It is an oracle database error that shows that the number entered in criteria is not converted correctly according to the locale of the database.
Same value in Search criteria works correctly.

So is this a bug?

Test case is on 11.1.2. It reproduce also in 11.1.1.4

I guess you need a database with different locale to reproduce (a locale that decimal ceparator is ',')

Bugs Review in jdeveloper 11.1.2

2011-06-19T02:35:00.000-07:00

I reviewed my posted bugs in latest release of jdeveloper 11.1.2
Posted bugs that still reproduce in latest version of jdeveloper are:

Combo box does not remember values in table

Invalid values in choice lists

Dependent LOV in table shows invalid values

Rollback does not refresh current row of af:table after validation errors.
http://adfbugs.blogspot.com/2010/03/rollback-does-not-refresh-current-row.html

Custom Attribute Validation on LOVs
http://adfbugs.blogspot.com/2009/11/attribute-validation-on-input-list-of.html

Number precision and scale
http://adfbugs.blogspot.com/2009/10/number-precision-and-scale-bug.html

Range paging and Table Selected Row Bugs
http://adfbugs.blogspot.com/2009/07/range-paging-and-table-selected-row.html

Tab selection and Enable User Customization on Session bug.
http://adfbugs.blogspot.com/2009/09/tab-selection-and-enable-user.html

Not Reproduced bugs in JDeveloper 11.1.2:

Jdeveloper 11.1.1.5 severe bug

Application Module cannot get principal when you use transaction controller in task flows

ExecuteEmptyRowSet and Range Paging.
http://adfbugs.blogspot.com/2009/09/executeemptyrowset-and-range-paging.html

Partial Page Rendering ChangeEventPolicy="ppr" bug.
http://adfbugs.blogspot.com/2009/07/partial-page-rendering.html

First jdeveloper 11.1.2 bug

2011-06-07T13:44:00.000-07:00

For start let me say that i am impressed positively with the new jdeveloper development experience.
Fast and furious
Yet I hit on the first bug already.
I used the default oracle three column layout and created a jsf page with a panel box
On runtime when I tried to disclose first empty column I got a java script error

Is it a problem of old template?
Is it a problem of combination of jspx template with Facelet page?
Will see…
Test case
http://adfbugs.googlecode.com/files/Application5.rar

Major : Jdeveloper 11.1.2 release

2011-06-07T12:03:00.000-07:00

Less than a month after the 'tricky' release of 11.1.1.5 the major release is here.
Not yet for SOA and Web Center.
Yet it is much earlier than i expected.
http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html
Lets hope it is the stable and promissing release we expected.
I have done over 10 migrations already of applications from TP1.
More than 3 every year, and it was a tricky task every time.
I am downloading at the moment.
Lets see...

Combo box does not remember values in table

2011-05-27T06:12:00.000-07:00

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)

2011-05-16T00:32:00.000-07:00

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)

2011-05-03T00:47:00.001-07:00

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

Invalid values in choice lists

2011-03-21T01:43:00.000-07:00

There are some cases that in database there are some values in fields that are not selectable any more in List for the specific fields.
For example there can be a lookup table for Status that some values can be selected by user and other that only the system can set.
An other case are Types that are not valid any more but exist for old data.
So if you have limited the data of a choice list with a where statement there is a chance that, data exist for the limited rows. The behavior of choise list then is quite problematic.

To demonstrate it in HR schema I limit the DepartmentView to have only departments that have managers (WHERE Departments.MANAGER_ID is not null) and jobs WHERE Jobs.MIN_SALARY<4000. In a simple adf form if you go to an Employee that has a department without a manager then the department choice list seems to have no value and 2 empty selections.
Also in the log you see the message:
ADFv: Could not find selected item matching value 210 of type: oracle.jbo.domain.Number in the list-of-values.
User thinks there is no department for employee and he can make changes (not on department) and save yet the department is not set to null.

If you go to an employee that has invalid job you see again the choice list empty, even though it has a value. If you try to change any other field and submit you get the required field error even though it has a value.

Similar issue exists when Choice List is dependent to another field. Then if you change the other field and choice list does not have a valid value any more it shows empty even though the value still exist in view object. In this case you need to define dependency on view attributes so that the choice list becomes null every time you change the other field. This way though the choice list value will be lost even if it is valid.

Test Case:

http://adfbugs.googlecode.com/files/TestChoiseLists.zip

Still reproduce in 11.1.2

SR and bug Bug 12320392: JDEV 11.1.1.4.0 INVALID ENTRIES IN SELECTONECHOICE
was posted for this. Yet it is rejected by the Oracle development team with the answer:
=== ODM Answer ===
From the Bug request # 12320392 - JDEV 11.1.1.4.0 INVALID ENTRIES IN SELECTONECHOICE
BDE team has answered as follows:

Currently there is no way to do this automatically for selectonechoice component. Which is why for this use case you should use af:inputListOfValues or af:inputComboboxListOfValues (ADF LOV Choice List).

Jhug

2011-03-19T02:37:00.000-07:00

Jhug is Java Helenig User group
http://www.jhug.gr/
It is a very active user group with great people that i had the pleasure to meet. Among others they organise monthly meetings in greece, discussing technology development and making presentations. I have attended 2 times and had the honor to make a presentation about jdeveloper 11g
http://adfbugs.googlecode.com/files/Jdeveloper%20IDE.pdf
I find this user group very usefull and helpfull and wish to continue like this.

Dependent LOV in table shows invalid values

2011-02-14T23:45:00.000-08:00

Dependent LOV in table sometimes show invalid values.
This is reproduced in Jdeveloper 11.1.1.3 and 11.1.1.4
For example lets say that there is a business rule that ‘The manager of an Employee must be from the same Department.’

To implement this we usually have a list of value for departments and a list of values for Managers that is depended from the department field. Also added dependency on ManagerId attribute to DepartmentId attribute.

I have created an updatable table with the above fields and added auto-submit and partial trigger properties

So for example (testTable.jspx)
When Department is Administration there are 2 selectable employees (189,200) for manager Id
When Department is Marketing there are 3 different selectable employees (190,201,202) for manager Id

It works correctly as long as there is no validation error in manager id field.

To reproduce the problem, do the following:

1. Select row for employee 190 that has department Marketing and type in ManagerId field the value 200.
2. Select an other row. A validation error shows for Manager Id.
3. Select again the same row and change Department to Administration. (Validation error continue to show)
4. open ManagerId LOV. The values shown are wrong (190,201,202). The ManagerId LOV is not refreshed according to Department.
5. Select or Type a value in field (i.e. 201 that is invalid) and press commit. The invalid value cleared. The row is saved to database with null value for manager id.

This issue does not reproduce in form layout (testForm.jspx) since Manager Lov always becomes null when department is changed.

It is quite confusing for the users.

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

Still reproduce in jdeveloper 11.1.2
The workaround we found for this is in managed bean to resetValue of the LOV component in the value change listener of choise list

Jdeveloper is Ready

2011-02-11T03:57:00.001-08:00

On the first release of jdeveloper 11, I had made a post that jdeveloper is not ready.
http://forums.oracle.com/forums/thread.jspa?messageID=2836045&#2836045

After 4 patches I feel now that jdeveloper 11.1.1.4 and ADF is ready to use for development of large scale enterprise applications.

The basic bugs have been minimized and the IDE have been stabilized.

We migrated the 46000 files (1GB) adf application to 11.1.1.4 without any serious issue apart from fixing the jazn-data.xml according to note 1288757.1 - Policy Migration of the "jazn-data.xml" File Fails Silently in JDeveloper 11.1.1.4.0.

We are also working now with java 64 bit on windows and set the following configuration :

Set in jdev.conf file (in $Middleware_Home$\jdeveloper\jdev\bin) depending on java installation path:
SetJavaHome D:\Java64\jdk1.6.0_23
AddVMOption -XX:MaxPermSize=1024M

Set in ide.conf file (in $Middleware_Home$\jdeveloper\ide\bin) depending on the available memory:

AddVMOption -Xmx2048M

AddVMOption -Xms512M

The low memory messages have been minimized.

I would like to congratulate the jdeveloper team for their work and wish the best for the future.

Still reproduced bugs in jdeveloper 11.1.1.4

2011-01-28T04:12:00.000-08:00

The most important bugs in my opinion that still reproduce in latest version of jdeveloper are:

Rollback does not refresh current row of af:table after validation errors.
http://adfbugs.blogspot.com/2010/03/rollback-does-not-refresh-current-row.html

Custom Attribute Validation on LOVs
http://adfbugs.blogspot.com/2009/11/attribute-validation-on-input-list-of.html

Number precision and scale
http://adfbugs.blogspot.com/2009/10/number-precision-and-scale-bug.html

Range paging and Table Selected Row Bugs
http://adfbugs.blogspot.com/2009/07/range-paging-and-table-selected-row.html

Tab selection and Enable User Customization on Session bug.
http://adfbugs.blogspot.com/2009/09/tab-selection-and-enable-user.html

ExecuteEmptyRowSet and Range Paging.
http://adfbugs.blogspot.com/2009/09/executeemptyrowset-and-range-paging.html

Partial Page Rendering ChangeEventPolicy="ppr" bug.
http://adfbugs.blogspot.com/2009/07/partial-page-rendering.html

Jdeveloper 11.1.1.4 resolved bugs

2011-01-22T00:35:00.000-08:00

I went through the bugs posted here and tried to reproduce them in new release of jdeveloper 11.1.1.4 patch set 3.
It seems many of them are resolved since I cannot reproduce them in the specific test chases. Those are:

Choice List Loose value in disclosed af:Query
http://adfbugs.blogspot.com/2011/01/coise-list-loose-value-in-disclosed.html

LOVs does not reset criteria values. Yet there is a new issue that second time you open LOV it displays same amount of rows as the first search but different.
http://adfbugs.blogspot.com/2010/11/lovs-does-not-reset-criteria-values.html

Activation creates duplicate row when primary key is populated through DB sequence
http://adfbugs.blogspot.com/2010/11/activation-creates-duplicate-row-when_15.html
http://adfbugs.blogspot.com/2010/11/activation-creates-duplicate-row-when.html

Passivation - Activation looses data of Subclassed Entities (Dimitris Stasinopoylos blog)
http://dstas.blogspot.com/2010/11/entity-inheritance-and-passivation.html

Choice list and LOV in query criteria bug
http://adfbugs.blogspot.com/2010/07/choice-list-and-lov-in-query-criteria.html

Range paging in LOVs throw SQL exception with specific steps
http://adfbugs.blogspot.com/2010/06/range-paging-in-lovs-bug-9467477.html

Choise list and checkboxes in popup turn to null after submit
http://adfbugs.blogspot.com/2010/05/choise-list-in-popup-turn-to-null-after.html

Single Row LOV in Query Criteria cannot clear value
http://adfbugs.blogspot.com/2010/05/single-row-lov-in-query-criteria-bug.html

User not populated to model and history collumns
http://adfbugs.blogspot.com/2010/05/user-principal-is-not-propagated-to.html

Composition Association and Locking
http://adfbugs.blogspot.com/2009/12/composition-association-and-locking.html

Bind Variable and View Criteria in view with range paging bug
http://adfbugs.blogspot.com/2010/02/bind-variable-and-view-criteria-in-view.html

Removing a LOV return value leaves garbage in view object
http://adfbugs.blogspot.com/2010/03/removing-lov-return-value-leaves.html

Auto Submit does not set the value in bindings if you navigate with mouse
http://adfbugs.blogspot.com/2010/04/auto-submit-does-not-set-value-in.html

Many Thanks to Oracle Developmnet team.

New Patch Set PS3 of JDeveloper (11.1.1.4) is out there

2011-01-16T01:11:00.000-08:00

New Patch Set PS3 of JDeveloper (11.1.1.4) is out there
http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html
From the release notes it seems to have a lot of bug fixes and some usefull new features.
http://www.oracle.com/technetwork/developer-tools/jdev/index-088099.html
http://www.oracle.com/technetwork/developer-tools/jdev/relnotes-14-jan-11-261400.html

From the basic components the most usefull new features for us will be:
• Column stretching of results table in search and select dialog
• Ability to configure column widths of inputComboboxListOfValues
• New API on the RichPopup component that complements the client-side API to show, hide and cancel a popup.

In the next weeks I will go through the bugs posted there and the SRs in Oracle Support to post what is fixed or not.

I hope there will be no new defects on existing functionality and that we can easily migrate applications to new patch

Choice List Loose value in disclosed af:Query (Fixed in 11.1.1.4)

2011-01-11T07:33:00.000-08:00

Choice lists seem to be quite sensitive on loosing their value. Apart from popups with full submit button, they loose their values also inside af:query component when it is closed and submited.
In a simple Query page with Query panel and result table I put some criteria values:

Then i close the Search panel and i press Submit button

When i open Search panel again the selected value in department choise list is lost

Is this a nice bug or what?
Test Case:
http://adfbugs.googlecode.com/files/TestDisclosedCriteria.zip

Happy new year 2011

2011-01-10T01:27:00.000-08:00

Happy new year to all.

I wish you all health (less physical bugs) and better productivity (less code bugs)

I would like to apologize for not beeing posting the last month.

It is not that we don't find bugs, it is just that we had a major milestone and a lot of pressure.

I will try to be more active from now on, as we are also expecting new versions of Jdeveloper this year and I will be more involved in other Fusion technologies , SOA, BPMN, WC etc. this year.

Posting for you soon

LOVs does not reset criteria values. (Fixed in 11.1.1.4)

2010-11-24T05:15:00.001-08:00

In a default input list of values you can set criteria to query for specific records and select a record with no problem
The problem is that if you open LOV again, even though the criteria values are cleared the results are still the same (filtered).This happens even if you change the record.
This has other side effects like, if LOV is autosubmit and if user types a valid value that does not exist in the previous filtered LOV data the value is not accepted and LOV opens displayed the previous filtered data.
Finally if you put criteria in LOV and select a value and then navigate away from the task flow, when you come back and open LOV the criteria values are shown and Reset button of LOV is not functional.
This functionality of LOVs cause much frustration to users.
Test Case :
http://adfbugs.googlecode.com/files/TestLOVsCriteria.zip

Steps to reproduce in the test case:
1. Not accepting valid values.
1 run Main.jspx
2 go to Test task flow.
3 open managerId LOV and type criteria (i.e. ‘A’ for firstName) and press search
4. Select a row and press ok
5. In LOV field, type a valid value of an employee that first name does not start with ‘A’ and press tab
Result: LOV opens showing rows of employees starting with A. User has to press Reset and search for the value again

* in 11.1.1.4 the valid value is accepted without opening the LOV. Yet if you open LOV second time the results rows are limited but not for employees starting with A.

2. Reset button does not work:
1 run Main.jspx
2 go to Test task flow.
3 open LOV and type criteria (i.e. ‘A’ for firstName) and press search
4. Select a row and press ok
5 Press button to Main (return from task flow)
6 go to Test task flow again
7 Open managerId LOV (Criteria values and results are visible from previous search
8. Press Reset Button on LOV (Nothing happens)
Result: LOV opens showing rows of employees starting with A and criteria value for firstName. User cannot press Reset to clear values and search again.

Activation creates duplicate row when primary key is populated through DB trigger ((Fixed in 11.1.1.4)

2010-11-15T06:41:00.000-08:00

The same issue as previus post is also reproduced if Primary key is populated through database trigger and Pk attribute is defined as DB Sequence and refresh after insert.

Fusion Developer's Guide for Oracle ADF

4.10.10 How to Get Trigger-Assigned Primary Key Values from a Database Sequence

To run the test case you need to create database trigger :

CREATE OR REPLACE TRIGGER LOCATIONS_PK
BEFORE INSERT
ON "LOCATIONS"
FOR EACH ROW
BEGIN
IF INSERTING
THEN
IF :NEW."LOCATION_ID" IS NULL
THEN
SELECT LOCATIONS_SEQ.NEXTVAL INTO :NEW."LOCATION_ID" FROM DUAL;
END IF;
END IF;
END;

When you try to insert second line, first line is dublicated, when testing activation safe.

Test case

http://adfbugs.googlecode.com/files/TestActivateSequenceDBTrigger.zip

Activation creates duplicate row when primary key is populated through DB sequence (Fixed in 11.1.1.4)

2010-11-12T03:03:00.001-08:00

We are testing if our Application Module is Activation-Safe according to:
Fusion Developer's Guide for Oracle ADF
40.10 Testing to Ensure Your Application Module is Activation-Safe
And we have many problems.
1 of them is that when we press createInsert instead of creating a new row we get the same row 2 times.

I reproduce it in a simple test case from HR schema with Countries and Locations Entities.
In Locations Entity create method I populate primary key from sequence

@Override
protected void create(AttributeList attributeList) {
super.create(attributeList);
SequenceImpl s = new SequenceImpl("LOCATIONS_SEQ",getDBTransaction());
setLocationId(s.getSequenceNumber());
}

As in
Fusion Developer's Guide for Oracle ADF
4.12.5 Assigning the Primary Key Value Using an Oracle Sequence

I check Activation-Safe by un-checking Enable Application Module Pooling in configuration.

I have a simple master Countries form and detail Locations table with CreateInsert button.
When I press CreateInsert for first time a new row is created with new sequence as locationId and I fill also other fields with values.

When I press CreateInsert again instead of getting a new rows I get 2 same rows as the first and both of them has the same new sequence as primary key.!!??

After that whatever I do on the page I get null pointer exception. (NullPointerException)
Is this a bug?

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

Number precision and conversion in query criteria

2010-10-15T02:55:00.000-07:00

There is a strange behavior of number type fields in af:query.
I created a simple Query page from HR schema for Employees (Entity and View) with some typical criteria.
When a user type a value in a String criterion field then he is not allowed to type more characters than the precision of the field.(i.e. 25 for LastName, email)
The same apply for the LOV field (Department 4 digits)
Yet Number fields have strange behavior.No mater the precision of the Number field you can type as many digits you want.
Yet if you type up to 21 then the last 4 digits are converted to 0!!?
If you type more than 21 digits it is converted to the first digits with other 3 as decimals!?
If you type number with more than 3 decimals it is rounded to 3 decimals.

These restrictions make large numbers not usable for query criteria.
Is this a bug to be fixed?
Test case:

http://adfbugs.googlecode.com/files/ViewCriteriaPrecision.zip

ADF/SOA custom worklist viewFilter

2010-10-10T02:09:00.000-07:00

I have managed to create a ADF application with a custom worklist region following instructions of :
Developer's Guide for Oracle SOA Suite &30.13 Creating Reusable Worklist Regions

It was not easy since
• WSRP Container is missing in latest jdeveloper 11.1.1.3
• when I deployed nothing was shown and no error in the logs.

I found out that WSRP Container seems not to be needed and that it was authorization issue.
Since the application must have security enabled, you need to give access also to task flows that comes from libraries:

Then the task list is visible and task details shows as dialog.

Yet we need to show to the user a custom view that contains Flex Fields with business logic values.
I see that there is a parameter you can pass to the worklist task flow the viewFilter:
Developer's Guide for Oracle SOA Suite &34.4 Passing Worklist Portlet Parameters
'viewFilter Specifies the selected view for which the tasks are displayed.'

Yet when I use it with values like:
value="Due Soon"
value="My Work Queues/Standard Views/Due Soon"
I get the following error:

Is this a bug or i need diferent format of value in order to filter specific task view?

I also noticed that from view menu all views shows 2 times apart from Inbox:

Is this also a bug?

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

Making View Criteria Case Insensitive and MDS

2010-09-24T03:55:00.000-07:00

In a previous post i had posted a workaround about making view criteria case insensitive:
http://adfbugs.blogspot.com/2010/07/making-view-criteria-case-insensitive.html
Yet this has 2 side effects.

It makes values of criteria upercase.
It brakes MDS save criteria functionality.

I found a simpler solution (workaround).
/**
* Set the view criteria rows to use case-insensitive querying and
* uppercase any of the non-null query-by-example criteria provided.
*/
private void doCaseInsensitiveOnStringsInViewCriteria() {
ViewCriteria[] vclist = getApplyViewCriterias(ViewCriteria.CRITERIA_MODE_QUERY);
if (vclist.length>0) {
for (ViewCriteria vc : vclist){
if (!vc.isUpperColumns())
vc.setUpperColumns(true);
}
}
}

@Override
protected void executeQueryForCollection(Object object, Object[] object2 int i) {
doCaseInsensitiveOnStringsInViewCriteria();
super.executeQueryForCollection(object, object2, i);
}
This code makes query criteria Case insensitive and also does not make values of criteria upercase.Yet it still brake MDS .
Sice we need this in LOV criteria that does not have Save search, we can prevent this code to execute in LOVs using :
if (this.getName().contains("LOCAL_VIEW_USAGE"))
doCaseInsensitiveOnStringsInViewCriteria();

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

Validating Train Flow

2010-09-11T04:19:00.001-07:00

A very nice option of Task Flows is the Train Task flow.

You can easily create a train task flow and add pages as Train stops and add in page train navigation and train buttons (Next/Previous) and create a wizard like navigation.

Yet many times you need to validate the input of a train stop before you go to the next one. When this validation is more complex than a required field you probably need to do it when the user tries to navigate to the next train stop.

I found a solution close to what I needed in Duncan Mills post: Executing Activities between Train Stops
http://groundside.com/blog/DuncanMills.php?blog=6&cat=18&page=1&disp=posts&paged=2
The strange thing is that you need to define an outcome on the target Train Stop activity.
Then you add a wildcard to go to a router to check your condition in order to decide to go to the target Train Stop or the source.

In my example the condition is if the Department has employees or not. If it has it go to employees page, if not it returns to department task flow.

The remaining issue is to show the appropriate message. In the example I have added it as a simple text that is visible when Department does not have Employees

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

MDS saved search brakes application module browser

2010-08-31T05:42:00.000-07:00

In order to save search criteria through MDS you need to add configuration in adf-config.xml according to Fusion Developer's Guide for Oracle ADF :
27.2.3 How to Persist Saved Searches into MDS
Yet after you do that if you try to run any application module you get exception:
(oracle.jbo.ConfigException) JBO-33003: Connection name hrconn is not defined.
and in server log:
SEVERE: MDSConfigurationException encountered in parseADFConfigurationMDS-01335: namespace "/persdef" mapped to metadata-store-usage "mdsstore" but its definition was not found in MDS configuration. oracle.mds.config.MDSConfigurationException: MDS-01335: namespace "/persdef" mapped to metadata-store-usage "mdsstore" but its definition was not found in MDS configuration. at oracle.mds.config.PConfig.populateNamespaceConfigList(PConfig.java:811) at oracle.mds.config.PConfig.loadFromBean(PConfig.java:717) at oracle.mds.config.PConfig.(PConfig.java:504) at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:692) at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:749) at oracle.mds.config.MDSConfig.(MDSConfig.java:407)
...

The workaround we found is to remove specific configuration and add it again when we want to deploy.
Is this a bug?
Test case:
http://adfbugs.googlecode.com/files/MDSTest.zip

MDS User customization capabilities and cost

2010-08-10T03:39:00.000-07:00

I was investigating lately MDS user customization capabilities and cost in order to apply it to our application.
I used the following References
Guides
34 Customizing Applications with MDS
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/customize.htm
35 Allowing User Customizations at Runtime
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/ad_persist.htm#CIHHEHCF
13 Managing the Metadata Repository
http://download.oracle.com/docs/cd/E15523_01/core.1111/e10105/repos.htm#CIHDCHCF

Articles
http://www.oracle.com/technology/pub/articles/adf-development-essentials/part8.html

Tutorial
http://www.oracle.com/technology/products/jdev/11/cuecards111/adf_set_18/ccset18_ALL.html
Blogs
http://biemond.blogspot.com/2009/07/customize-and-personalize-your-jsf.html
http://andrejusb.blogspot.com/2009/09/persisting-query-criteria-results.html

I created a demo application:
http://adfbugs.googlecode.com/files/MDSTest.zip
Where user1/welcome1 has customizations:

And user2/welcome2 has not:

And tested also our application with MDS enabled
I came up with the following conclusions :

User customization Persist user changes through MDS is very powerful framework and all users would like to have it, yet it has it limitation and its cost:

Limitations:

1. Save Search: If you Use MDS then you need to configure also Saved search, or else you get exception when you try to save it
2. Components Not all components and attributes are persisted by default and they might override your custom business logic.

3. Deployment: New deployment file is needed (MAR) and configuration in order to define MDS repository domain. Investigation is needed for continues integration and deployment processes and update deployment scripts

Cost
> Performance
-- Increased resources needed on weblogic (memory and disc io)
-- Increased resources needed on database (mds_repository)
-- Lower response time on customisable components
> Increase testing needs
> Increase Administration needs (database, weblogic, metadata management)
> Saved search may break integration between Pages. Workaround may be needed for specific search pages. This will increase development needs
> Increase Support needs.

Choice list and LOV in query criteria bug (Fixed in 11.1.1.4)

2010-07-21T05:51:00.001-07:00

We have a strange bug in our application.
When ever in query criteria we have choice list as first criterion and we have also input List of values in criteria then the input List of values does not return values.
When you open LOV and select a row the LOV closes automatically and value is not returned.

I managed to reproduce it in simple test case in HR schema with 1 choice list and 1 list of values:

The workaround is either not to use choice list as first criterion or not to have Input List of values field autosubmit = true.

Strange?

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

Making View Criteria Case Insensitive.

2010-07-09T07:47:00.000-07:00

When you create view criteria you can easily set in each string criterion if it should be Case sensitive or not by checking or unchecking 'Ignore Case'.

Yet the default view criteria used in LOVs or criteria of fields added in advanced search are always Case Sensitive and you cannot declaratively change that.

I found a realy old post of Steve Muench for similar case in very old release of jdeveloper

http://www.oracle.com/technology/products/jdev/howtos/10g/dynamiccrit/index.html

and managed with little changes to apply it in latest release also:

Now all view criteria for string fields are case insensitive.

Note that this implementation will override any criterion you have set as Case Sensitive.
You can add this code to your base view object so that all view objects work like that.

test case:
http://adfbugs.googlecode.com/files/TestCaseInsensitive.zip

Table input text resize while typing non latin characters/ output text not selectable

2010-07-01T01:54:00.000-07:00

In af:table input fields have a nice animation while you type non latin characters.
As long as you type characters the width of the field becomes smaller:

I have tested with Greek and Turkish characters.
If you mouse over the field it returns to the correct width.

Is this a bug?

Also there is no way you can select a value from the output fields in order to copy it.

These are quite frustrating for the users

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

Always run weblogic servers as Administrator

2010-06-21T03:12:00.000-07:00

I spend all weekend trying to install SOA suite at home.
I have a new i7 pc with windows 7 and 4G ram.
After spending hours on installing:
-->11g database,
-->Repositories with rcu (failed the first time because of database parameters processes and open_cursors must be 500)
-->Java bridge
-->Lookback adapter.
-->Weblogic 10.3.3.
-->Application development runtime 11.1.1.2 and 11.1.1.3
-->SOA Suite 11.1.1.2 and patchset 11.1.1.3

I try to run admin server and I got many exceptions … class not found … invalid variables, deployments failed.

So I thought I did something wrong and I did the hall thing again (from the weblogic part). But still the same ??!!. Then it came to me…
I right click on Start Admin server and I choose run as Administrator… and eurica!! All went smoothly.

I used the same way to open cmd windows to run managed servers:
-->first soa_server took 20 minutes to deploy all applications
-->then bam_server
Everything worked fine now.

Yet the memory consumption of my pc went to 3GB, and everything was operating really slowly after that.

So I suggest… don’t try this at home…

Range Paging in LOVs bug #9467477

2010-06-14T02:13:00.000-07:00

Using Range Paging in LOVs is fixed in new jdeveloper 11.1.1.3.
http://adfbugs.blogspot.com/2009/07/performance-tuning-lovs-and-range.html

Yet it still has bugs, when you use LOV criteria or on dependent LOV sometimes it shows error:

java.sql.SQLException: Missing IN or OUT parameter at index:: 1 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)

I have posted an SR for this and bug was logged #9467477 SQLEXCEPTION: MISSING IN OR OUT PARAMETER AT INDEX, IN LOV WITH RANGE PAGING, that it is also fixed for next jdeveloper 11.1.1.4 release. Thanks Didier.

I decided to post it also here since this bug is not public visible in Support (not even for me that i posted the SR.

Steps to reproduce in test case are:
1. Open Departments LOV
2. Scroll down to LOV until fethcing data message apears
3. Type in criteria for departmentId value i.e.'1' and without pressing Search select a row in LOV.SQL
Error message apears:

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

Entity Security (jdeveloper11.1.1.3 Functionality Change)

2010-06-07T07:36:00.000-07:00

After Migration to new jdeveloper we found out that users that had no permissions to update entities could insert and save new records!!!???

I managed to reproduced in a simple test case with 1 entity Jobs on an editable table.
I have enabled security and I have 2 roles ‘UpdateJobs’ and ‘ViewJobs’.

I have added authorisation to entity update and delete for role UpdateJobs.

When I loggin with a user that just have ViewJobs role table rows comes read only and Delete button disabled.

Yet CreateInsert button is enabled and if I press it new row is created with updatable attributes that I can also save it without a problem.

Before last patch you could still create new row but it was not updatable.
Is this a bug?

Test case:
http://adfbugs.googlecode.com/files/TestInsertSecurity.zip
password for User and Manager : welcome1

ADF Client Tag Libraries of weblogic 10.3.3 installation are diferent from jdeveloper11.1.1.3

2010-06-02T04:28:00.000-07:00

Latest weblogic 10.3.3 installation and jdeveloper11.1.1.3.0 installation software
http://www.oracle.com/technology/software/products/middleware/index.html

have different adf faces component ligraries.

We found it the hard way.
We used the new feature of popups the autoCancel property.
Even though in embeded weblogic is working, when we deployed we had a jsp compilation error:

Error message: Failed to compile JSP /pages/bill/billissue/billIssue.jspxbillIssue.jspx:792:23: This attribute is not recognized. autoCancel="disabled"> ^--------^ Error type: class weblogic.servlet.jsp.CompilationException

by searching the differences we found out that
Oracle/MiddlewareR1P2/oracle_common/modules/oracle.adf.view_11.1.1/adf-richclient-impl-11.jar!/META-INF/afu.tld
in jdeveloper 11.1.1.3
is different than
wsl_middleware/oracle_common/modules/oracle.adf.view_11.1.1/adf-richclient-impl-11.jar!/META-INF/afu.tld
of the weblogic 10.3.3. installation
The weblogic afu.tld does not have the autoCancel property

We hope that by just copying the jdeveloper11.1.1.3 adf-richclient-impl-11.jar to weblogic the problem will be fixed.

Unfortunately, just copying the jar did not solve the problem

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

SR posted :3-1820014361

It seems that you need to manual install on latest weblogic 10.3.3. tha latest adf runtime libraries.
You can find how to on:
Oracle Support Knowledge base Note [ID 1094153.1] Installing ADF 11.1.1.3 Runtime Into FMW 11gR1 Patchset 2
or http://theblasfrompas.blogspot.com/2010/05/installing-adf-runtime-into-fmw-11gr1.html

Choise list in popup turn to null after submit (Fixed in 11.1.1.4)

2010-05-31T06:52:00.000-07:00

After migration we have strange behavior in popups with choise list, file upload and other components.
I managed to reproduce it in a simple test case with a table and a Edit popup with a simple choise list.
The first time i open popup it looks ok

If i press 'Submit' button (full submit) the popup is closed as expected since it is autoCancel enabled.

But if i open popup again, then the coise list is empty!!??

This causes other side effects. I.e. if you have partial trigger in popup components from page table, then when you change a line after you have closed popup with submit you get the following error:

The following does not happen if you press the ok/cancel dialog buttons or x button.

The workaround we are using is not to use full submit buttons in popups, and close popup programaticaly in backing bean:

public void closePopUp(String popUpId){
FacesContext facesContext = FacesContext.getCurrentInstance(); ExtendedRenderKitService service = Service.getRenderKitService
(facesContext, ExtendedRenderKitService.class);
service.addScript(facesContext, "AdfPage.PAGE.findComponent('templateid:"+ popUpId
+"').hide();");
}

Also with autocancel = enabled, then a partial submit button and a partial trigger on popup or on parent component will close the popup without problem.

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

Single Row LOV in Query Criteria Bug (Fixed in 11.1.1.4)

2010-05-26T02:42:00.000-07:00

When List of values has only 1 row then in query criteria you cannot set input to null after the first time you set a value.

To reproduce in the test case of Employees with Departments LOV i set where clause of DepartmentsView rownum=1.

I assign DepartmentsView as LOV in Employees.DepartmentId attribute and set it to autosubmit.

I put DepartmentId in query criteria of Employees.

I create a simple query panel with results table for Employees and i run application:

Steps to reproduce:
1. open DepartmentId LOV and select value. press tab or search
2. delete value of DepartmentId and press tab or search
Result: value is not deleted from LOV field. and search still has the criterion.

Only way to make value null is to press reset button.

Is this a bug?

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

ADF and DBA have 2/3 letters in common

2010-05-14T03:59:00.001-07:00

I was doing DBA work this week. We installed our application in different schema and the performance dropped to hell.

The View objects queries that we spend a lot of time tuning in previous schema now they had different execution plan.

So I check the instance properties and I see OPTIMIZER_MODE=ALL_ROWS.
This option means that when you do a query the optimizer thinks that you are trying to retrieve all data from the query so it check the statistics to find the best plan to retrieve all rows usually by full table scans. The all_rows mode is generally used during batch-oriented processing and for data warehouses where the goal is to minimize server resource consumption.

This is not the case in our application and I guess in most ADF applications. I changed it to OPTIMIZER_MODE=FIRST_ROWS. The first_rows optimizer_mode is generally used in online system where the end-user wants to see the first page of query results as quickly as possible. This had a huge positive effect in the performance of our fusion application.
May be this is considered basic for DBAs but it seems that ADF developers should know also in order not to loose time tuning view objects in a wrong configured database.

User principal is not propagated to Middle tier. New bug on 11.1.1.3. (Fixed in 11.1.1.4)

2010-05-06T00:17:00.000-07:00

It may be strange that a new bug like that is introduced in a bug fixing release but it can happen to the best also.

After Migrating to jdeveloper 11.1.1.3.0 you will notice that application module method getUserPrincipalName() return always ‘Anonymous’ and history columns for user are populated with null. Andrejus Baranovskis have posted about it, Steve Muench logged on Oracle Metalink - bug# 9672139 and a workaround is posted also in the comments that we also use and seams to solve the problem.
I post it also to follow upe with it.
On our base Application Module class we override the prepare session and:

@Override
protected void prepareSession(Session session) {
String contextUser = ADFContext.getCurrent().getSecurityContext().getUserName();
String envUser = (String)session.getEnvironment().get(PropertyMetadata.USER_PRINCIPAL.getName());
if (!envUser.equals(contextUser)) {
session.getEnvironment().put(PropertyMetadata.USER_PRINCIPAL.getName(),contextUser);
}

super.prepareSession(session);
}

Still reproduced bugs in jdeveloper 11.1.1.3

2010-05-04T00:02:00.000-07:00

Fixed Defects in 11.1.1.3

2010-05-03T01:34:00.000-07:00

I went through previus posted bugs and verified that the following defects are fixed in new version of jdeveloper:

LOV execute query many times
http://adfbugs.blogspot.com/2009/08/lov-execute-query-many-times.html

Range Paging in Master Detail bug.
http://adfbugs.blogspot.com/2009/08/range-paging-in-master-detail-bug.html

Af:Query bind variable bug
http://adfbugs.blogspot.com/2009/08/afquery-bind-variable-bug.html

LOV view object Tuning: 'Only up to row number' bug
http://adfbugs.blogspot.com/2009/08/lov-view-object-tuning-only-up-to-row.html

Query Component Required Criterion bug ( r1 Bug)http://adfbugs.blogspot.com/2009/07/query-component-required-criterion-bug.html

New Bind Variable and View Criteria bug
http://adfbugs.blogspot.com/2010/01/new-bind-variable-and-view-criteria-bug.html

Selectively required criteria in LOV
http://adfbugs.blogspot.com/2010/01/selectively-required-criteria-in-lov.html

Required Criterion on Choice List type Attribute.
http://adfbugs.blogspot.com/2010/01/required-criterion-on-choice-list-type.html

These are quite important Fixes for us since they improve LOV functionality that we commonly use and view criteria. They also improve the performance of these controls.

A new version of JDeveloper is out: JDeveloper 11.1.1.3.0 (Build 5660)

2010-04-28T01:07:00.000-07:00

A new version of JDeveloper is out: JDeveloper 11.1.1.3.0 (Build 5660)
You can download it from OTN.
New features and bugs fixed list is available [Here]

It is mostly a bug fixing release.
some bugs reported as fixed seems to be related to bugs of this blog:

8975151 RFI:UNABLE TO USE VO RANGE_PAGING OPTION IN LIST OF VALUES

D8B2-BLK:PRJ:LOV THROWING NPE AFTER DISABLING AMPOOLING.

9149095 RFI: RANGE PAGING JSF PAGE RETURNS TOTAL ROW COUNT IN GETFETCHEDROWCOUNT()

I will walk through the bugs reported till now and try to reproduce them in new release and i will post a list of fixed and still reproduced bugs

Inserting new rows as last row of table

2010-04-21T01:10:00.000-07:00

By Default when you add a new row on table (or view object) it is added before the current selected row.

End user requirement was that when we press Insert the new row should be added as last row no matter which is the current row.

This is implemented by overriding the View Object method insert(row).
/**
* Insert new Rows at the end of RowSet.
* @param row
*/
@Override
public void insertRow(Row row) {
//go to the end of Rowset if it has rows
Row lastRow = this.last();
if (lastRow != null) {
//insert new row at the end and make it current
int indx = this.getRangeIndexOf(lastRow) + 1;
this.insertRowAtRangeIndex(indx, row);
this.setCurrentRow(row);
} else { // empty Rowset
super.insertRow(row);
}
}

Note: This could cose performance issue when inserting new rows on very large tables.

Don’t forget in table components to always set displayRow="selected" so that the new row to be visible no matter how many rows there are.

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

Auto Submit does not set the value in bindings if you navigate with mouse (Fixed in 11.1.1.4)

2010-04-16T02:08:00.000-07:00

Auto Submit does not set the value in bindings if you navigate with mouse.

You can test that by debuging an input field by typing a value and go to an other field using mouse, the setter of the field is not called. Yet the value change listener is invoked.

This causes problem in dependent components also since they will be recalculated with the old value.

For example in dependent LOV by navigating away from the dependant field with the mouse it does not cause the LOV to re-execute with the new value so you may have validation error even if the value of LOV field is correct, or you may have wrong filter in LOV.

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

The workaround we use in such cases is since the value change listener of DepartmentId is invoked to explicity set also the binding field value there. Like:

ADFUtils.setBoundAttributeValue("DepartmentId", valueChangeEvent.getNewValue());

Unique Key Validator on Entity does not work correctly

2010-04-12T06:52:00.000-07:00

Unique Key Validator on Entity does not work correctly. Even if you have valid data in your entities, since it checks also database values it shows validation error.
Also after that in table components validations messages does not show after a refresh of browser, data change automatically to database values without showing an error.

For example in simple department Entity i create an alternative Key for DepartmentName to be unique.

Then i add an entity Unique Key Validation for this key:

I run a page with departments table and i create 2 departments
1 Dep1
2 Dep2

If i change department 1 name to dep2 then i correctly get the validation error:

But if i change department 2 to dep1 then i get unique validation errors even if both values in entities would be unique.

This could be logical for the developer since he knows that each row is validated seperately but not for the user.

Also if i refresh page in browser then if i do the same thing i dont get validation errors.

If i commit new values are not saved and database values are displayed back.

Is this working as expected?

Test Case:

http://adfbugs.googlecode.com/files/TestUniqValidation.zip

Type Map change corrupt project metadata.

2010-04-06T02:59:00.001-07:00

According to Type Map description :For an application running against an Oracle database, you can usually accept the default. Note: You can select the type map only when you first initialize your business components project.

Yet the developer still can change it at any time. At first it shows disabled but if you click something else and click Bussiness Components tab again then you can change it.

If you change it to java, then Entity attributes are generated with types like (BigDecimal instead of oracle.domain.Number, java.sql.Date instead of oracle.domain.Date)
If you change them to oracle types then at some adf components you get ClassCastExceptions.

If you try to chance Type Map to ‘Oracle’ again then you cannot. Even though it shows in project properties changed if you close and re-open it is still ‘Java’.

The only way to change it back to ‘Oracle’ is to open .jpx project file and to manually remove the xml entry --Attr Name="_jbo.TypeMapEntries" Value="Java" –

Oracle ACE awarded

2010-03-30T01:48:00.000-07:00

I was recently nominated by Steve Muench and awarded with the Oracle ACE title.

I would like to thank Oracle and especially Steve for this recognition of my efforts to contribute to Oracle community my experience on Oracle products

This blog has been proven to be quite helpful to people working on ADF framework since they can find bugs and workarounds to save them time while developing fusion applications.

It has also helped to submitting bugs on Oracle Support and improving the framework,

I definitely try to do constructive criticism on the framework, as I feel very strongly about its potential and I hate to see it being compromised by implementation or occasional design issues. Fact is, there is nothing like it out there for rich client web development.

I am glad that Oracle people also see it this way and I will continue this effort to the best of my abilities.

Removing a LOV return value leaves garbage in view object (Fixed in 11.1.1.4)

2010-03-24T02:26:00.000-07:00

We had a strange bug that was really hard to find. We found some garbage in View objects that we could not find out how they were created. Yet I manage to reproduce it by removing a return value from Edit List of values wizard. In more detail :

When you have an LOV with 1 return value then the xml in the view object is like:

When you add a second return value from LOV by edit wizard:

Then the View object XML is like:

If from the same wizard I remove the second value then unfortunately the xml does not return to the initial state. It still has the DerivedAttrNames :

This causes various bugs in interface that are not easy to find, since nothing is displayed in log:

The workaround is to remove garbage by hand from xml.

Test case:

http://adfbugs.googlecode.com/files/TestLOV.zip

Rollback does not refresh current row of af:table after validation errors.

2010-03-17T07:41:00.000-07:00

In a simple af:table if you select a row and press CreateInsert then new row is created with focus above the selected row.

If you press Rollback then the selected row is by default the first row of the table.

This works fine.

Yet if before rollback you have validation errors (i.e. After creating a row, navigate to an other row), then rollback does not make the first row selected.

Selected row on table remains the last selected row even if the current row of view object is the first row.
If you press now CreateInsert, the new row is created as first row of table and it does not even have the focus.

If you click now on the empty row then you will get again the validation errors.

Is this a bug?

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

Still Reproduce in jdeveloper11.1.2
SR 3-2391480761 and defect was posted for this yet it is Rejected by development team as:
Our Development team has marked this as expected behaviour and therefore it will not be fixed in the future either - at least not for now.

Cascading LOV in detail view dependent on master view attribute

2010-03-08T07:15:00.001-08:00

In some cases we have LOVs in detail view objects that are dependent on an attribute on a master view object.

For example in Departments Employees Master detail, you want to have a list of values for Employees managers to be the department Manager or employees that have the department manager. The LOV query would be :
select *
from employees
where manager_id = :inManager
or employee_id = :inManager

In the view accessor for the LOV you can set the bind variable of the LOV to get value from the master view object ‘DepartmentsView.ManagerId’ or in the employees view object you can add Departments entity and add attribute ManagerId from Departments Entity.

Yet when you change Manager of the Department in both cases the LOV does not know that the bindVariable value has changed and it is still executed with the old value of Department value.

This is happening because the LOV is notified to take new bind value when the setter of the dependent attribute is invoked.

In order to do that I created an updatable transient attribute LOVManagerId that on the getter when it has no internal value it gets the value from Departments entity reference attribute.

public Number getLOVManagerId() {
if (getAttributeInternal(LOVMANAGERID)==null)
return this.getDepartmentManagerId();
return (Number) getAttributeInternal(LOVMANAGERID);
}

Now on the getter of reference entity attribute I check if entity attribute has changed in order to set also the LOVManagerId.

public Number getDepartmentManagerId() {
Number empdepManager = (Number) getAttributeInternal(DEPARTMENTMANAGERID);
if (this.getDepartments().isAttributeChanged("ManagerId"))
this.setLOVManagerId(empdepManager);
return empdepManager;
}

Partial triggers form Department.ManagerId field to Employees table will finish the job.

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

Limit Query Results based on custom property

2010-02-26T03:56:00.000-08:00

In ADF, for performance reasons you need to limit the results of the query of a view object. Also you need to inform the user that the results are limited so that he will know that he need to put specific criteria to find specific records.

You can use up To Row Number property in view object tuning, yet this just limit the fetched records and not the query.

You can use Range Paging option. Yet data for each row must be posted before you change row, so that makes it hard to use on view objects used for transactions.
So if a view object is based on entity that has many data it make it hard to tune.

An option for better performance is to use performance tip on tunning FIRST_ROWS and at the same time to limit the results of the query adding in where clause ‘ROWNUM <= :queryLimit’. In order to do that generic and not to change where clause of queries for each view object you need to tune, I use a custom property on view object ‘QueryLimit’ In the ViewObjectImpl

I override method executeQueryForCollection and, if there is a 'QueryLimit' property on view object then it apply a limit to the query of view object "ROWNUM <=QueryLimit" before performing query. Also after query I set the property "ResultsLimited" to "true" if queried records are not less of the QueryLimit.

I also have a method that checks ResultsLimited and return a message that the results are limited. I expose that method to client and use it from backing bean to show message to the user when results are limited.

We have put the logic in our base ViewObjectImpl class so it can be used from every view object
This approach boosted the performance in our application, of transaction pages that was based on tables with large amount of data.

Test Case

http://adfbugs.googlecode.com/files/LimitQueryResults.zip

GoMenuItem with target="_Blank" in Menu workaround

2010-02-19T00:43:00.000-08:00

In a go menu item inside first Level of menu when we select goMenuItem 1 then new window opens behind my window (internet explorer 7,) works correctly in mozilla

We found a workaround for this case as follows.

We add client Listener in go menu item to execute a java script method
that remove the focus from the current window.

function focusoff(event)
{
blur(event.source);
}

This way the new window opens above the current window.

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

New Cascading LOV with required View Criterion Not a Bug

2010-02-11T07:54:00.001-08:00

On july 2009 in the patch of jdeveloper (11.1.1.1.0) a new feature was introduced in view criteria. When a criterion is required then an error message is shown to user. Of course not without side-effects (http://adfbugs.blogspot.com/2009/07/query-component-required-criterion-bug.html)
On the latest patch of jdeveloper (11.1.1.2.0) a new feature and bugs was introduced in view criteria (http://adfbugs.blogspot.com/2010/01/new-bind-variable-and-view-criteria-bug.html)
The above bugs also effected the functionality of LOVs especially of those that use view criteria, either for selective required (http://adfbugs.blogspot.com/2010/01/selectively-required-criteria-in-lov.html) or for cascading LOVs.

In the current test case I have Employees and I want the List of value of Managers to depend on the department of the employee. I expect when the user has not selected a department the List of values of managers to be empty

Yet when I run application, just when I set department to null I get the following error.

ADF: Adding the following JSF error message: Attribute DepartmentId is required.
oracle.jbo.AttrValException: JBO-27035: Attribute DepartmentId is required.
at oracle.jbo.rules.JboVCItemRequiredValidator.validateItem(JboVCItemRequiredValidator.java:91)
at oracle.jbo.rules.JboVCItemRequiredValidator.validate(JboVCItemRequiredValidator.java:161)
at oracle.jbo.common.ViewCriteriaImpl.validateRow(ViewCriteriaImpl.java:606)
at oracle.jbo.common.ViewCriteriaImpl.validate(ViewCriteriaImpl.java:567)
at oracle.jbo.server.ViewRowSetImpl.validateViewCriteria(ViewRowSetImpl.java:7745)
User will think that DepartmentId is required, yet only the hidden criterion of LOV is required.

But actually it is just a warning, since if I press ok and submit then the new values are submitted, even though the value of ManagerId is not valid.

If I open ManagerLOV I get again the error and the LOV opens with no data.

If I clear the value of Manager I get the error again.

This is realy confusing and makes view criteria not usable in cascading LOVs.

The workaround we do for these cases is not to use view criteria for cascading LOVs but to put conditions directly in the where clause of the query.
i.e. WHERE DEPARTMENT_ID = :inDepId

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

Thanks,
Anonymous said... In this case, all you need is to set "Validation" to "Optional" and leave "Ignore Null Values" un-checked.

I tried it and works fine.

Rollback to same row with view criteria workaround

2010-02-08T05:57:00.000-08:00

Rollback for Forms and ADF means that we re-query data from database and remove changes that the user did.

From the user side of view rollback is expected to return to him to the same state he was when he last saved data.

So when the user that work on a Form (Row) presses Rollback and looses the row that he was working on is really confusing for him.

Fortunately Steve Muench has issued a workaround for this that many people use now in ADF applications.
http://blogs.oracle.com/smuenchadf/examples/
68. Restore Current Row After Rollback

Yet the above workaround does not work when View criteria are applied in view object and latest changes committed does not comply with these criteria.

This happens because Rollback forces query to re-execute with the applied view criteria and the changed (current) row does not exist in the new results set.

So for example in the current application there is a query and an edit page.
If you Query departments for specific manager (i.e. 100) and go to edit page if you change manager (i.e. to 200) and commit, after that if you press rollback you will loose that row since there is no longer in the queried rows.

I have applied a workaround in the current test case for that issue. In the beforeRollback of the view object I add a View criteria row that matches the current row primary key. This causes the current row always to comply to view criteria when we press rollback since in the query it is added
WHERE …. or (PK_FIELD = CURRENT_ROW_KEY)

In method afterRollback I remove the specific criteria row so that if the user query again (not by rollback) the results without the current row to be fetched.

This way the current row is not lost when it does not comply with applied criteria and we press rollback.

This workaround we have implemented in our Base ViewObjectImpl class and works also with composite primary keys.
The only issue is that with applied view criteria with no values the ‘or’ operator does not apply and only the current row remains in the result set after the rollback.

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

Bind Variable and View Criteria in view with range paging bug (Fixed in 11.1.1.4)

2010-02-01T06:12:00.000-08:00

I managed to reproduce bug described in

http://adfbugs.blogspot.com/2010/01/new-bind-variable-and-view-criteria-bug.html

in a simple query page for view object with Range paging tuning.

When you query with a department then Reset and then Query again after scrolling and selecting rows, it throws exception:
java.sql.SQLException: Attempt to set a parameter name that does not occur in the SQL: inDeptId

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

Required Criterion on Choice List type Attribute.(Fixed in 11.1.1.3)

2010-01-25T04:49:00.000-08:00

Trying to replace some inputListOfValues fieds that have small amount of data with choiseList components we fall into the following.

If the choice list attribute is used in view criteria as a required criterion then even if you select a value, validation error ‘Error: A value is required.’ Still shows up.

This happens even when attribute is set to autoSubmit.

Is this a bug?

We use input list of values instead as a workaround.

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

Selectively required criteria in LOV (Fixed in 11.1.1.3)

2010-01-18T05:11:00.000-08:00

In order to improve performance in LOVs I tried to set selectively required criteria, so that the query of LOV should always run with some parameters.
So in simple department LOV in employees.departmentId attribute I put view criteria with selectively required option.

Also as in test case :
http://adfbugs.blogspot.com/2009/08/lov-execute-query-many-times.html
I override the method executeQuery for collection and print the query:

@Override
protected void executeQueryForCollection(Object object, Object[] object2, int i) {
System.out.println("EmployeesLOV executes Query :" + this.getQuery());
super.executeQueryForCollection(object, object2, i);
}

When I run application and open LOV and select a value, in log I see that 3!? Queries are executed:

Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments WHERE ( ( (UPPER(Departments.DEPARTMENT_NAME) LIKE UPPER( :vc_temp_1 '%') ) ) )
Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments WHERE ( ( ( (UPPER(Departments.DEPARTMENT_NAME) LIKE UPPER( :vc_temp_1 '%') ) ) ) AND ( ( (Departments.DEPARTMENT_ID LIKE :vc_temp_2 ) ) AND ( ( (UPPER(Departments.DEPARTMENT_NAME) LIKE UPPER( :vc_temp_3 '%') ) ) ) ) )
Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments

The Last query without any criteria !?

If I just type a valid value to the field and press tab then 4!? Queries are executed:

Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments WHERE ( ( (Departments.DEPARTMENT_ID LIKE ( :vc_temp_1 '%') ) ) )
Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments WHERE (Departments.DEPARTMENT_ID = :fbkKy__0)
Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments WHERE ( ( (Departments.DEPARTMENT_ID LIKE :vc_temp_1 ) ) AND ( ( (UPPER(Departments.DEPARTMENT_NAME) LIKE UPPER( :vc_temp_2 '%') ) ) ) )
Query : SELECT Departments.DEPARTMENT_ID, Departments.DEPARTMENT_NAME, Departments.MANAGER_ID, Departments.LOCATION_ID FROM DEPARTMENTS Departments

The Last query again without any criteria !?

So you don’t gain much in performance of LOV since the query is executed many times again and without any criteria.

Also sometimes when you just type a value, you get the PPR exception, or an invalid value exception even if the value is valid.

Steps to reproduce:
1. Run TestLOV page
2. open department LOV, type A in DepartmentName criterion and press search
3. Without selecting a row press OK or cancel.
4. Type a valid value to LOV (i.e. 50) invalid value message appear.

5. Open LOV again, press OK or cancel then press submit button

oracle.jbo.AttrValException: JBO-27036: At least one of the following attributes DepartmentName, ManagerId is required. at oracle.jbo.rules.JboVCItemRequiredValidator.validate(JboVCItemRequiredValidator.java:172) at oracle.jbo.common.ViewCriteriaImpl.validateRow(ViewCriteriaImpl.java:606)

It seems that Selectively required criteria in LOV has some issues.

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

New Bind Variable and View Criteria bug

2010-01-12T06:45:00.000-08:00

In the last patch of jdeveloper (1.1.1.2.0) there are a lot of improvements and bug fixes in view criteria functionality.

1 of the bug fixes is the performance of view criteria that had optional bind variables.

For example if in the Employees View you had optional criterion for departmentId with bind variable ‘inDeptId’ then in the query of the view object with applied view criteria in the where clause it was added ( (Employees.DEPARTMENT_ID = :inDeptId ) or :inDeptId is null )

Yet this adds a large execution time when inDeptId was null since it is forcing a full table scan.

After the last patch when you define optional criterion for departmentId with bind variable ‘inDeptId’ the where added is (Employees.DEPARTMENT_ID = :inDeptId ) and the optional part is implemented by removing the where clause expression.

Yet this dynamic change of query depending on parameters values sometimes throw exception:
(java.sql.SQLException) Missing IN or OUT parameter at index:: 1

I manage to reproduce it in a simple test case in Application Module Browser.

Steps to reproduce:
1. Open EmployeesView1
2. Press Search button (Specify View Criteria)
3. Select EmployeesViewCriteria and press find
4. set departmentId = 10 and press ok
5. Repeat 2-4 but set departmentId = null (empty)

The following exception appears.

If you create a simple search page with query panel and results table then you can’t reproduce this. It is reproduced in our application when we programmatically change view criteria values and execute, but I can’t identify specific conditions

Is this a bug?

Anyone else has run into this?

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

Happy New Year

2010-01-04T00:45:00.000-08:00

2009 was my first year of posting in this blog and I must say that I really enjoyed it.
Mostly because of the fact that you read this and you post constructive comments.

I will continue to post defects this year also, even though interesting defects are getting harder to find.

That is actually a good thing. May be I will upgrade this blog to also post defects that developers use to create.

Any other ideas are welcome.

Happy new year to everyone

Composition Association and Locking (Fixed in 11.1.1.4)

2009-12-22T01:36:00.001-08:00

We had a lot of locking problems in our ADF application even though we use optimistic locking.

We found out that it was caused by composition Association and Lock Top Level Container Option.
This is the default way the association is generated by the wizard when the foreign key constraint in database is cascade.
In my test case I set it by hand to reproduce in Department Employees relationship.

The master Entity Table in database is locked every time you create a new record in the detail composed entity.
This is happening when creating detail data and not when posting data as in optimistic locking
This does not happen when you update or delete data from detail entity.

Is this a bug?

If pessimistic mode of Application Module is not a good practice for Fusion Applications then composition Association Locking should also be not.

Composition Association is a rule to prevent details to exist without a master. But this is also prevented if the foreign key attribute in detail entity is required. So I also don’t see the usage of composition association.

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

GoMenuItem and GoLink with target="_Blank" don't work correctly inside a Menu

2009-12-16T00:15:00.000-08:00

We have strange behavior with GoMenuItem and GoLink components inside menu items

To reproduce the problem i created the following simple test case:
Created a menu with 2 levels and gomenuItems and MenuLinks that all open 'otn' in new '_blank' window.

The menu is the following:

1. In the menu above if i select goMenuItem 1 then new window opens behind my window (internet explorer 7,) works correctly in mozilla. goMenuItem 2 works correctly in ie7 also.

Funny thing is that if in ie7 you have a second tab opened then it works correctly.

2. goLink 1 works correctly, goLink 2 does nothing.

Is this a bug? any workaround?

test case:
http://adfbugs.googlecode.com/files/TestGoMenuItem.zip

Pending changes in ADF application

2009-12-14T05:34:00.000-08:00

So far I have seen 2 ways to check if there are pending changes in ADF application

1 is from ApplicationModule.getDBTransaction().isDirty();

2. is from DataControlFrame.isTransactionDirty();

Yet their functionality is not the same.
To demonstrate it I created a master –Detail, Departments - Employees test case with backing bean that return :

public String getAmChangesExist() {
BindingContext bc = BindingContext.getCurrent();
ApplicationModule am = bc.getDefaultDataControl().getApplicationModule();
return am.getTransaction().isDirty()?"True":"false";
}

public String getDcFramechangesExist() {
BindingContext bc = BindingContext.getCurrent();
String currentDataControlFrame = bc.getCurrentDataControlFrame();
return bc.findDataControlFrame(currentDataControlFrame).isTransactionDirty()?"True":"false";
}

If I change anything on department(except TransientAttribute) or employees and press submit then both methods show there are pending changes.

Yet if I change value of transient attribute only dataControlFrame.isTransactionDirty() shows there is a change, and am.getTransaction().isDirty() shows false

If I press button createInsert on Department or on Employees then again :
dataControlFrame.isTransactionDirty() shows there is a change, and am.getTransaction().isDirty() shows false

I feel that changes should not include transient attributes that dont exist in entities, since they are not used in transaction.

But it should include new rows created on views and entities.

In order to be sure i would chose dataControlFrame.isTransactionDirty() since it also keeps its value even with diferent application modules through task flows with shared data control scope.

Test case:

http://adfbugs.googlecode.com/files/TestPendingChanges.zip

Dynamic Region UIShell

2009-12-06T02:35:00.000-08:00

I had created a Dynamic Region Template before the release of new jdeveloper patch.
Since there is a lot of discussion about the new Oracle UI Shell I decided to share it as I feel it is:

Simpler
Easier to use
Uses Dynamic Regions to navigate to different task flows
Provides customized functionality about navigating while having pending changes
Supports security permission check for navigating between task flows

The source code of the DynamicUIShell is here.

I also created a demo application based on HR schema, that uses this template to show the functionality. http://adfbugs.googlecode.com/files/TestDynamicUIShell.zip

In this demo you can run test page and see the functionality.
You can navigate between Home, employees and departments task flows.

If you make a change and try to navigate to an other task flow a popup raises and rollback if you chose continue.

If you try to navigate to Secured task flow a popup inform you that you don't have permission.

How to use Dynamic Region UIShell

Just import the jar file in your view controller project.

Then when you create a new JSF page you can select the template 'DynamicUIShell'.

Now you have the page based on the template.

First thing needed is to define the DefaultRegion , the task flow to be rendered in main area when the page is loaded.

i.e. f:attribute name="DefaultRegion" value="HomeTaskFlow"
Now the page should be functional and display the DefaultRegion task Flow.

Adding navigation components.

You can add now navigation components in facets like Global, TopMenubar, LeftToolBar.
Navigation components can navigate to other pages or display a different Task Flow in the main area.
In order for navigation components to be functional 2 properties are needed:
ActionListener should call navigate method of dynamicRegion managed bean (that exist in library).
Id of the component must be the path and name of task flow inside WEB-INF (with / character replaced with _):

Adding pending changes popup.

In order for pending changes to be checked a popup is needed to be added to your page, with your custom message and a Continue button.
The popup must be binded to dynamicRegion managed bean changesExist popup
The Continue button must have actionListener to dynamicRegion managed bean method continueNavigation method.
If you want to Rollback before navigation the Rollback action must exist in page definition.

Adding no permission popup

In order to check permission (taskFlowViewable) you need to add a popup on your page binded to noPermissionPopup of dynamicRegion managed bean.

Also when security is enabled in your application don't forget to allow access also to the template. To see the template in your jazn-data you need to select 'Show web pages imported from ADF libraries' check box.

Any feedback is usefull.

Issues after migrating our application from jdeveloper 11.1.1.1.0 to 11.1.1.2.0

2009-11-30T00:15:00.001-08:00

1. In windows XP pro, when the integrated weblogic is running we get the following exception about adrci.exe . Yet after that everything seems to be working ok.

2. We call many task Flows by url, in order to open them in new window. After migration they gave 403 error.

There is a new property added in Task Flows definition URL invoke that we needed to set it to url-invoke-allowed in all task flows called like that.

The only documentation I found about that is in

15.6.4 How to Call a Bounded Task Flow Using a URL

…The default value (calculated) allows a URL to invoke the bounded task flow if the bounded task flow does not specify an initializer and it has a view activity as its default activity. If the bounded task flow does not meet these conditions, a HTTP 403 status code is returned…

Yet even though we had no initializer and we had default activity we still got HTTP 403 and had to change to url-invoke-allowed

3. We have many tables that have check box based on a view object Boolean attribute. After migration the attribute value was always set to null no matter checked or unchecked.

The workaround was to remove in view objects from those attributes the control type ‘check box’ as Tilemahos in oracle forums found

http://forums.oracle.com/forums/thread.jspa?threadID=985720&tstart=30

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

ActionListener and showPopupBehavior

2009-11-28T02:01:00.000-08:00

Many times developers complain that actionListener of a button is not invocked when they add a showPopupBehavior. Yet that is not a bug.

By default showPopupBehavior the action type is Action that is a client event and does not invoke server actions. That is described in af:showPopupBehavior documentation:

The af:showPopupBehavior tag is a declarative way to show a af:popup in response to a client-side event. The client event is specified using the triggerType attribute. The "action" event is the default triggerType if one is not provided.
....
All actionListener method bindings and associated action listeners will not be invoked when the triggerType of "action" is used.

So the solution is to just set the triggerType of ShowPopupBehavior to click.

Then the actionListener and popup are invoked.

Test Case:

http://adfbugs.googlecode.com/files/TestPopupBehavior.zip

Setting value programmatically on required field.

2009-11-24T04:14:00.001-08:00

It is common requirement when you set a value in one field to also set a value to a second field.

This we usually do on setter of view object of the first field or the valueChangeListener also by adding a partialTrigger on the second field.

Yet if the second field is required and the previous value is null then nor the setter nor the valueChangeListener are invoked because of validation error.

This is because the partialTrigger is trying to refresh the second field before even submitting the first field.

Is this a bug or intended behavior?

The workaround we found is to remove partial trigger from second field and on valueChangeListener of the first field to use addPartialTarget

In the test case when you select department we want to set manager also, so in the setter of department id there is:
public void setDepartmentId(Number value) {
setAttributeInternal(DEPARTMENTID, value);
this.setManagerId(new Number(100));
}

Also managerId field is set required=true

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

Carousel does not make the selected row current

2009-11-22T13:57:00.000-08:00

Carousel is a realy nice new component in jdeveloper 11 patch1
When you create a data binded carousel item it just uses an iterator and a tree model as a table.
Every item in carusel is from a diferent row of the iterator.
Yet when you select a new item the current row of the iterator is not changed.
So if you want to have other fields of the same iterator in the page or detail view objects iterators the data are not refreshed while navigating in Carousel.
I think a selectionListener as in the table component is missing.

In order to achieve the above behaviour i did the following:
I binded carouselSpinListener property to a backing bean method where
i get the carusel event NewItemKey and i find the Key of the row and i set iterator current row to the carusel selected row.
public void caruselSpin(CarouselSpinEvent event) {
List l =(List)event.getNewItemKey();
Key k = (Key)l.get(0);
DCIteratorBinding iter = getDCBindingContainer .findIteratorBinding ("DepartmentsView1Iterator");
iter.setCurrentRowWithKey(k.toStringFormat(true));

}

Now Every time you select new item in carusel the iterator has the selected row.

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

Still reproduced bugs in jdeveloper patch 1

2009-11-15T03:27:00.000-08:00

Fixed bugs in jdeveloper patch 1

2009-11-15T03:21:00.000-08:00

New Feature Closing a Popup can now be captured.

2009-11-13T11:04:00.000-08:00

My first impression of patch 1 of jdeveloper11 is that it looks like a new IDE,
diferent screens for overview and for security,
diferent menus and lots of new properties.

One thing that was missing and I was complaining about in the oracle forums was the capturing of an event when a popup dialog is closed.
http://forums.oracle.com/forums/message.jspa?messageID=3898637#3898637

Now a new property in popup component popupCanceledListener solves this problem.

You can just assign a backing bean method on it and it works no mater how you close the popup (with Cancel, with 'x' button or with ESC key).

This was realy needed. Thanks oracle team for the new feature

The only little bug in this is that in design view the popup is not visible when you place it in button facet popup

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

Patch set 1 of Oracle JDeveloper 11g is now available

2009-11-11T10:41:00.000-08:00

Oracle JDeveloper 11g (11.1.1.2.0) (Build 5536) is now available for download at
http://www.oracle.com/technology/software/products/jdev/htdocs/soft11.html

I will try to reproduce all bugs posted until now in this blog and will log the results shortly.

returnListener from dialog page not invoke when pressing x button

2009-11-10T00:12:00.000-08:00

In a button that opens an other page as dialog if you define a returnListener method in managed bean then when you return form dialog page by a button that has af:returnActionListener then it works fine.

But if you close the dialog page with explorer x button then return listener is not invoked!

i also noticed a worning in log:

WARNING: The application is running with the new window detect flag off. It is highly recommended that this flag be turned on to ensure proper functioning of your application when new browser windows are launched. In web.xml set the context parameter oracle.adf.view.rich.newWindowDetect.OPTIONS to 'on'.

But even when i did that there was no difference appart from no worning.

Is this a bug?

How can we ensure that when a dialog closes (no matter how) a method will be executed?

Test case:

http://adfbugs.googlecode.com/files/TestDialogReturn.zip

Attribute Validation on Input List of Values attribute

2009-11-06T01:53:00.000-08:00

If you have an attribute validation in an Entity Attribute that is used in a view object as Input List of values then validation does not work correctly.

For testing i added a simple validation in departmentId of Employees Entity that it should be less than 100:

I set departmentId as Input List of values and autosubmit.
When I run the page and i select an invalid department then the value is not set to the field and i have no validation Error

So in the page it looks that nothing have changed. But if i submit the page, the invalid value appears in department and the error message also.

So is this a bug?

The workaround we are using is to filter LOV to show only valid values to select, or to override the setter of the entity, which i do not consider as a good practice.

test case:
http://adfbugs.googlecode.com/files/TestLOVValidation.zip

Returning Multiple values from LOV in af:query with bind variables bug

2009-11-03T04:23:00.000-08:00

We get nullPointerException when returning multiple values from LOV in view criteria with bind variables.

To reproduce it in EmployeesView for departmentId I added LOV that also return ManagerId.

It work fine for Forms (TestForm) and for tables(TestTable), but not for af:query with bind variables:

I created 2 view criteria with departmentId and ManagerId, 1 with bind variables and 1 with no bind variables. And 2 pages 1 for each
TestQuery1 with af:query with bind variables
TestQuery with af:query with no bind variables

When trying to select department in TestQuery1 we get:

Caused by: java.lang.NullPointerException
at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfCriterionValues.(FacesCtrlSearchBinding.java:2834)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfAttributeCriterion.(FacesCtrlSearchBinding.java:1732)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfConjunctionCriterion._loadCriterionList(FacesCtrlSearchBinding.java:2775)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfConjunctionCriterion._loadCriterionList(FacesCtrlSearchBinding.java:2725)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding$AdfConjunctionCriterion.getCriterionList(FacesCtrlSearchBinding.java:2633)
at sun.reflect.GeneratedMethodAccessor840.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

Yet TestQuery return correctly departmentId and ManagerId.

So I guess the workaround is not to use bind variables in view criteria.

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

Workaround for Page Fragment Design view when using resource bundle

2009-11-01T01:41:00.000-07:00

Since the layout of the fragments i am working on was messed up due to bug:

http://adfbugs.blogspot.com/2009/10/page-fragment-design-view-is-messed-up.html

I was working on the structure view and i noticed the following worning:

So i thought what will happen if i move c:set deeper inside the tree:

And then the Design view is back to normal! and no problems at runtime also.

Note: It must be above all components that use c:set.

Page Fragment Design view is messed up when using resource bundle

2009-10-25T08:24:00.001-07:00

Design view of pages in jdeveloper is very usefull to find and layout components.

Yet in page fragments the Design layout is messed up when you use resource bundle for texts.

In the test case i created a simple page fragment with oracle default template and added 2 panel boxes:

but if i try to Select Text Resourse for Panel Box Title, the design view of the fragment is messed up.

You cant work any more in design view.

When you run application it looks ok, but not having a design view in fragments is quite a problem.

If i remove c:set component from the fragment then the Design view is fixed, but the text from bundles does not show in run time.

Is this a bug?

Test case:

http://adfbugs.googlecode.com/files/TestFragmentDesignView.zip

How to check and throw exception after all data are posted

2009-10-20T04:48:00.000-07:00

Thanks to Oracle Suport and Didier Laurent a workaround is found to problem:

http://adfbugs.blogspot.com/2009/10/open-locks-in-optimistic-locking-bug.html

By Design optimistick locking locks before doCommit.

In order to remove locks and not loose entities data and to restore entity states, set the configuration parameter jbo.txn.handleafterpostexc to true.

Thanks Didier and Oracle Suport.

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

Number precision and scale bug

2009-10-17T07:17:00.000-07:00

Milos showed me this bug the other day and I could not believe it.

Number precision and scale does not work correctly in default ADF input field.

I searched metalink, I could not find something relevant

I reproduced it in a simple test case with Employees view object.

Employees Table has Salary field which is NUMBER(8,2) and CommissionPct NUMBER(2,2)
I also added a field on Employees table TO_PAY which is NUMBER(20,5)
I created a default input form.

When I try to enter value 123456.78 to salary which is a valid value I could not enter 8 digit
When I try to enter value 0.12 to CommissionPct I could not enter either 1 or 2 digit
When I try to enter value -123456789012345.12345 to ToPay field I could not enter the last 2 fields.

This issue is because when you drag and drop items on page it set precision the precision of the number ignoring fragment separator, sign symbol or 0 before fragment separator.

This is defined in input field property: maximumLength="#{bindings.Salary.hints.precision}"

You can eather remove maximumLength or set it to "#{bindings.Salary.hints.precision+1}" for Salary or +2 for percentages or even +3 for cases that you have only fragment digits like CommissionPct but you could also put negative number.
Take also into account that in some locale the negative number may have (###) format, meaning that you need +4 on maximumLength.

Also the number converter does not work correctly for numbers with more than 3 digits.
I tried to put 12345.12345 in ToPay field but when I submit I get back 12345.123 loosing the last 2 digits.

I try to fix this by setting ToPay converter min and maxFractionDigits
af:convertNumber groupingUsed="false"
pattern="#{bindings.ToPay.format}"
minFractionDigits="5" maxFractionDigits="5"

then I could enter, see and submit all 5 fraction digits.

But when I try on an empty field to put number 123456789012345.12345 it is automatically converted to 123456789012345.12000 when I press tub. When I change it again it works ok.

Are these bugs?

Test case:
[http://adfbugs.googlecode.com/files/TestDigits.zip]

No inconsistency check after any Exception during posting data

2009-10-13T01:07:00.000-07:00

During working on previous bug I found out that after any exception while posting Entity Data, inconsistency is not checked again.

Normally if 2 users query same row and change it then the user that commits last will get RowInconsistentException (JBO-25014)

But if second user get any exception while posting i.e. Foreign Key constraint exception, and then he correct it and commit again then he never gets a RowInconsistentException (JBO-25014)

To reproduce it in test case do the following

Run application and for ManagerId of department put an number that does not exist. Try to commit and you get constraint exception.

Open new instance of application and change anything and commit.

Go back to the first application correct the ManagerId to a valid value and commit.
You don’t get any RowInconsistentException

Is this a bug?

test case:

http://adfbugs.googlecode.com/files/TestInconsistency.zip

Open Locks in optimistic locking bug !!!

2009-10-09T09:52:00.000-07:00

Open Locks in optimistic locking bug !!!

Yes it is possible, it was happening in our application and could not imagine why.
After research we found out that it was in the CustomDBTransactionImpl.
We use it to override doCommit in order to do staff after all data are posted but not yet committed according to :
Fusion Developer's Guide for Oracle ADF, D ADF Equivalents of Common Oracle Forms Triggers:

POST-FORMS-COMMIT
Execute code after Forms has "posted" all necessary rows to the database, but before issuing the data commit to end the transaction

If you want a single block of code for the whole transaction, you can override the doCommit() method in a custom DBTransactionImpl object and write code before calling the super.

I managed to reproduce it in a simple test case.

I just have Departments entity and view and an application module with CustomDatabaseTransactionFactory. In CustomDBTransactionImpl I override doCommit and throw an exception:

@Override
protected void doCommit() {
if (true){
throw new JboException("Exception in doCommit");
}
super.doCommit();
}

I run the application, make a change and press commit. I get the error:

Now the row is locked in the database!!!!

I run a new instance of the application i make a change and try to commit and I get:

If I try to do rollback before I throw the exception then the locks are lost of course but also all the changes made on page.

Is this a bug?

If not, is there an other way to check and throw exception, after data are posted to database and before commit, without locking?

test case:http://adfbugs.googlecode.com/files/TestLock.zip

unexpected error on graph preview when security enabled

2009-10-05T12:23:00.000-07:00

I was trying to create graphs in a demo application with good results.
Jdeveloper 11 graphs are realy cool
Yet when i tried to put 1 in my application i got the known following error everytime i tried to preview graph in graph wisard.

i thought it was the selected data but, when i run application it seems ok

When i look at the messages tab of jdeveloper i see:

Caused by: oracle.security.idm.IMException: oracle.security.jps.JpsRuntimeException: The realm jazn.com does not exist. at oracle.security.jps.internal.idstore.xml.idm.IdmXmlIdentityStoreFactory.createIdmXmlIdentityStore(IdmXmlIdentityStoreFactory.java:182) at oracle.security.jps.internal.idstore.xml.idm.IdmXmlIdentityStoreFactory.createDefaultIdentityStore(IdmXmlIdentityStoreFactory.java:405) at oracle.security.jps.internal.idstore.xml.idm.IdmXmlIdentityStoreFactory.getIdentityStoreInstance(IdmXmlIdentityStoreFactory.java:196) at oracle.security.jps.internal.idstore.AbstractIdmIdentityStore.initStore(AbstractIdmIdentityStore.java:119) ... 60 more

So it had to do with security.

I enabled security in demo application and i have the same error again when i try to preview any graph from the wisard.

Is this a bug?

Test case:

http://adfbugs.googlecode.com/files/GraphTest.zip

user: tester

psw: welcome1

Tab selection and Enable User Customization on Session bug.

2009-09-29T05:18:00.001-07:00

When you have enabled User Customization for duration of session then what ever user changes on a page it remains the same through out the session, ie. Disclosed panel boxes, advanced query criteria, visible columns of tables in panel collections etc.

The problem is that you cant customize which properties to be kept or not :
Fusion Developer's Guide for Oracle ADF & 34.3 Configuring User Customizations:
Note: If you've enabled just session persistence, then all attribute values shown in Table 34-1 will be persisted to the session. There is no way to override this either globally or on an instance.

The bigger problem is that if you have some business logic about these components appearance or behavior you can’t override user settings.

We usually have some business logic about Disclosed tab in af:panelTabbed so I created this test case.

It’s a simple page that when you enter first tab should be disclosed and when you press button ‘Select Second tab’ second tab should be disclosed.

So I set disclosed property of First tab disclosed. Also on value change listener of button I run the following backing bean method:
public void SelectSecondTab(ActionEvent actionEvent) {
this.firstTab.setDisclosed(false);
this.secondTab.setDisclosed(true);
}

This work fine when I don’t have enabled User Customization.

But when I have enabled User Customization for duration of session then page always open with disclosed tab the one that I had selected the last time I used the page and backing bean method does not select the second tab.

Is this a bug?

Shouldn’t business logic methods override user customization settings?

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

Range Paging and Restore Current Row After Rollback workaround

2009-09-16T01:50:00.000-07:00

We use Steve Muench example for restoring current row after rollback is executed.
http://blogs.oracle.com/smuenchadf/examples/
http://otn.oracle.com/products/jdev/tips/muench/restorecurrencyonrollback/RestoreCurrentRowAfterRollback.zip
It was working fine until we started using Range Paging on view objects.
In view objects with range paging, if you select a row in the first page of range then rollback keeps the same row.

But if you select a row that is not on the first page of range, rollback gets you to the first row or throw a null pointer exception.

Reviewing the code of afterRollback method

public void afterRollback(TransactionEvent TransactionEvent) {
super.afterRollback(TransactionEvent);
if (currentRowKey != null) {
Key k = new Key(currentRowKey.getAttributeValues());
Row[] found = findByKey(k, 1);
executeQuery();
…

I noticed that it was calling executeQuery() method. I moved that call tbefore the findByKey method, and then rollback restores the current row after rollback even for view objects with Range Paging :

public void afterRollback(TransactionEvent TransactionEvent) {
super.afterRollback(TransactionEvent);
if (currentRowKey != null) {
executeQuery();
Key k = new Key(currentRowKey.getAttributeValues());
Row[] found = findByKey(k, 1);
…

Is this magic?

Do I miss something? Or it should be like that?

test case:
http://adfbugs.googlecode.com/files/TestRollbackRow.zip

Unsaved changes uncommittedDataWarning bug

2009-09-09T10:20:00.000-07:00

I was reading JDeveloper 11g — Functional Patterns & Best Practices for unsaved changes

http://www.oracle.com/technetwork/testcontent/unsaveddatawarning-096556.html

and decided to try it.

I created 2 task flows and 2 pages and navigation between them, normal and as dialog

In both pages i set and i run application.

I make a change in department name and press Employees Dialog.

The warning message for changes apear.

But the Employees Doesn't open as dialog!!??

When i try to return to Departments i get again the warning, even though no changes in this page and its a different task flow

So with this feature

you cannot use dialogs,

it does not rollback data

it does not depend on page or on task flow.

you cannot change the message

you cannot add custom logic on it

The only good thing about this feature is that the warning shows also when you try to close the explorer window. I wish it was working only then and it also released the application module.

test case:

http://adfbugs.googlecode.com/files/TestPendingChanges.zip

ExecuteEmptyRowSet and Range Paging. (Fixed in 11.1.2)

2009-09-06T02:54:00.000-07:00

As andrejus showed you can reduce the time loading a page by executing Empty row set before page opens.
http://andrejusb.blogspot.com/2009/08/oracle-adf-tuning-preventing-sql-query.html

Yet this does not combine with Range Paging since getEstimatedRowCount give result in an empty row set when Range paging is used.

To test that i created an Employees view object and a method in application module that executes empty row set and estimate row count:

public long emptyRowSetCount(){
this.getEmployeesView1().executeEmptyRowSet();
return getEmployeesView1().getEstimatedRowCount();
}

this return 0 in default view object.

but if i set Employees view object Access Mode = Range paging then the method return the count of rows of the database.

The getFetchedRowCount return 0 in both cases but this is not exposed in the bindings and on the pages we usually use #{bindings.EmployeesView1Iterator.estimatedRowCount}.

In ViewObjectImpl java doc, the method executeEmptyRowSet does not have any comments, so its not clear what it does.

So i wander if this is an issue of executeEmptyRowSet or getEstimatedRowCount or Range Paging...

Test Case:
http://adfbugs.googlecode.com/files/TestEmptyRowSet.zip
Not Reproduced in jdeveloper 11.1.2

LOV execute query many times (Fixed in 11.1.1.3)

2009-08-30T08:16:00.000-07:00

Input list of values component has big performance issues, and it seems not suitable for view objects with a lot of data.
Not only you cant use performance tuning since there are bugs if you use range paging:
http://adfbugs.blogspot.com/2009/07/performance-tuning-lovs-and-range.html
and Up to row number:
http://adfbugs.blogspot.com/2009/08/lov-view-object-tuning-only-up-to-row.html

but also because every time you open LOV and select a value it execute query many times.

To test that, i override the method executeQuery for collection and print the query:

@Override
protected void executeQueryForCollection(Object object, Object[] object2, int i) {
System.out.println("EmployeesLOV executes Query :" + this.getQuery());
super.executeQueryForCollection(object, object2, i);
}

when i open the lov and select a value i get the following log:

EmployeesLOV executes Query :Select * from Employees
30-Aug-2009 17:25:04 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( ( (EMPLOYEE_ID = :vc_temp_2 ) ) ) )
EmployeesLOV executes Query :Select * from Employees

so the LOV query is executed 3 times !?

If i type a value to fields that many LOV values start with this value then it is executed many times !!!.

EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID LIKE :vc_temp_2 ) ) )
30-Aug-2009 17:31:34 oracle.adfinternal.view.faces.renderkit.rich.RichRenderKit isNavigating
SEVERE: The original view root was not set.
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID LIKE :vc_temp_2 ) ) )
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID LIKE :vc_temp_2 ) ) )
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID LIKE :vc_temp_2 ) ) )
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID LIKE :vc_temp_2 ) ) )
EmployeesLOV executes Query :SELECT * FROM (Select * from Employees) QRSLT WHERE ( ( (EMPLOYEE_ID = :vc_temp_2 ) ) )
EmployeesLOV executes Query :Select * from Employees

Also while you scroll up and down in LOV the query is also executed many times.

Finaly if you type a value that many LOV values start with this value and scroll down then other values that dont start with this value are visible:

And if you select the value then you get a strange error:

Is this a bug?

Is there a way to use LOVs with a lot of data?

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

For the test case i put in Employees table about 100000 rows with the following procedure:

create or replace
PROCEDURE CREATE_EMPLOYEES AS
BEGIN
FOR i IN 1..100000 LOOP
Insert into employees (employee_id,
last_name,
email,
hire_date,
job_id)
select employees_seq.nextval as employee_id,
'auto' i as last_name,
'aut' i '@gmail.com' as email,
sysdate as hire_date,
'IT_PROG' as job_id
from dual;
END LOOP;
COMMIT;
END CREATE_EMPLOYEES;

Af:Query bind variable workaround

2009-08-19T02:34:00.000-07:00

When you try to enter a page that has af:query with bind variable, after ExecuteWithParams, it always keeps the first value that we first entered the page.
http://adfbugs.blogspot.com/2009/08/afquery-bind-variable-bug.html
Steve Muench said...
Filed bug# 8809022 with your testcase, thanks.
WORKAROUND----------
Rather than using the ExecuteWithParams action as the task flow'sinitial activity, instead write a custom AM method that you publishon the AM's client interface that does the following:
public void initTaskFlowDefinition(Number deptno) {
// Set var value on VO's variable
managergetEmployeesView1().ensureVariableManager().setVariableValue("inDepId",deptno);
// Save the save of the view criteria to "remember"
// the current var values as the ones to be restored
// in the search form.
getEmployeesView1().getViewCriteriaManager().getViewCriteria("EmployeesViewCriteria").saveState();
}
Then, have the task flow's default activity invoke this AMmethod instead to accomplish the task.

So i do it according to Steve workaround, but i didnt want to use bind variables since they have other issues:
http://adfbugs.blogspot.com/2009/07/jdeveloper-11-r1-cascading-lov-bugs.html
http://adfbugs.blogspot.com/2009/07/view-criteria-with-exists-optional-bug.html

So i used the following code:
public void initialSettings(oracle.jbo.domain.Number depId) {
EmployeesViewImpl emp = (EmployeesViewImpl)this.getEmployeesView1();
ViewCriteria vc = emp.getViewCriteria("EmployeesViewCriteria");
vc.first().setAttribute("DepartmentId", depId);
emp.getViewCriteriaManager().getViewCriteria("EmployeesViewCriteria").saveState();
}

i use this method in the task flow before entering the page and it seems to work fine.
Test Case:
http://adfbugs.googlecode.com/files/TestViewCriteria.zip

Range Paging in Master Detail bug. (Fixed in 11.1.1.3)

2009-08-14T03:41:00.000-07:00

When i thried to set Range Paging in some view objects in our application i had the following exception:

oracle.jbo.InvalidOperException: JBO-25011: Rowset Employees_Departments1_EmpDeptFkLink_DepartmentsView_0 is forward only. at oracle.jbo.server.ViewObjectImpl.validateRangeSizeForRangePaging(ViewObjectImpl.java:13522) at oracle.jbo.server.ViewRowSetIteratorImpl.setRangeSize(ViewRowSetIteratorImpl.java:529) at oracle.jbo.server.ViewRowSetImpl.setRangeSize(ViewRowSetImpl.java:2633) at oracle.jbo.server.ViewObjectImpl.doCreateViewLinkAccessorRS(ViewObjectImpl.java:13534) at oracle.jbo.server.ViewObjectImpl.createViewLinkAccessorRS(ViewObjectImpl.java:13624) at oracle.jbo.server.AssociationDefImpl.get(AssociationDefImpl.java:405) at oracle.jbo.server.ViewAttributeDefImpl.get(ViewAttributeDefImpl.java:773) at oracle.jbo.server.ViewRowStorage.getViewLinkAccessorResult(ViewRowStorage.java:1365) at oracle.jbo.server.ViewRowStorage.getAttributeInternal(ViewRowStorage.java:1579) at oracle.jbo.server.ViewRowImpl.getAttributeValue(ViewRowImpl.java:1795) at oracle.jbo.server.ViewRowImpl.getAttributeInternal(ViewRowImpl.java:783) at model.EmployeesViewRowImpl.getMasterDepartment(EmployeesViewRowImpl.java:522)

This happens if you use a master Accessor in a detail view object.
So i reproduced in a simple test case:

I have a simple Departments Employees master detail relation.

In Employees view object i create a transient Attribute IsDepartmentManager that i want to check if the employee is the manager of the department.

To do that i need the department assecor in Employees. so i do that from the View link.

In the getter of transient attribute i get the attribute of master :
public Boolean getisDepartmentManager() {
Object depManager = this.getMasterDepartment().getAttribute("ManagerId");
return depManager != null && depManager.equals(this.getEmployeeId());
}

When i Run application, everything is working fine:

But if i set Range Paging on tuning of Departments View and run again :

Is this a bug?

Am i missing something?

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

Table Filter Bug

2009-08-12T10:11:00.000-07:00

I create a default ADF table with filter from Employees views.

If i put an invalid value in date filter then i correctly have a validation error.

Also if i press rollback the value is cleared

If i put invalid value in a number filter then i get a ppr exception.

is this a bug?

Generally rollback (and resetActionListener) does not clear filters of table.

Is there a way to clear values and reset query for table filters?

Af:Query bind variable bug (Fixed in 11.1.1.3)

2009-08-09T00:38:00.000-07:00

We have noticed in our application a bug that when we enter a page that has af:query with bind variable, after ExecuteWithParams, it always keeps the first value that we first entered the page.

I reproduced this bug in a simple Departments Employees Test case:

In Employees View object i have a query criteria for DepartmentId = :inDepId. In the taskflow that opens the Employees query page i first run ExecuteWithParams for the task flow input paramter.

When i run application in the main page i select a department and then i pass DepartmentId as input value to the Employees task flow.

The first time i call Employees task flow everything works fine. The value of input parameter is set in the criteria and Employees of that department are queried:

But when i return to departments and select an other department and go to Employees again, the bind Variable in Query criteria is still the same, Even though the input parameter and the results have changed for the new department.

Isn't this realy strange?

If i change value and press reset it allways return to the first value that af:query is executed.
I tried in bindings refresh conditions and TrackQueryPerformed="Page" with no luck.

Is this a bug?

Is there a workaround?

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

Page with Region Validations bug

2009-08-08T03:01:00.000-07:00

In the same test case of previus post i put commit actions.

I noticed that if i have a validation errors in region i cannot submit or commit page.

In the contrary if i have validations on page i can do submit and commit on retion.

These problems are easily fixed if you put partial trigger in page components from region

But even though validations fire, if i dont have validation errors when i commit the region also the page changes are commited. but the page does not know it. The commit button is not becoming disabled.

In order to be more obvious i also added a field from Jobs in the main page.

Then if i change value in the region and press commit in the region the value is returned to the value of the main page.

Is this a bug?

If not, how can i refresh data of main page when i make a change in the region?

Region and dialog return bug

2009-08-06T11:16:00.000-07:00

I create a simple application with Departments and Jobs entities and view objects.

I put Departments as a simple form in a page and Jobs as a simple form in a page fragment and task flow that i add as a Region in the first page. I also create a dummy dialog with a return button.

But when i return from dialog and try to navigate inside the region i get the following error:

java.lang.IllegalStateException: ADF_FACES-60058:Attempt to re-register component with different model. at oracle.adfinternal.view.faces.activedata.PageDataUpdateManager._registerComponent(PageDataUpdateManager.java:256) at oracle.adfinternal.view.faces.activedata.PageDataUpdateManager.registerComponentForPPR(PageDataUpdateManager.java:161) at oracle.adf.view.rich.activedata.ActiveComponentContext.popActiveComponent(ActiveComponentContext.java:371) at oracle.adf.view.rich.render.RichRenderer.encodeAll(RichRenderer.java:1191) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:335) at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:751) at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:415)

After that the page is no longer functional.

Is this a bug?

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

P.s. This bug was found by 2 female colegues (Roula and Nota) in our application. It was working befor r1 of jdev11.

LOV criteria bug.

2009-08-05T10:40:00.000-07:00

Some times after using search criteria inside an LOV we get a strange exception:

java.sql.SQLException: Attempt to set a parameter name that does not occur in the SQL: vc_temp_2
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
at oracle.jdbc.driver.OraclePreparedStatement.setObjectAtName(OraclePreparedStatement.java:11158)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObjectAtName(OraclePreparedStatementWrapper.java:815)
at oracle.jbo.server.OracleSQLBuilderImpl.bindParamValue(OracleSQLBuilderImpl.java:4617)
at oracle.jbo.server.BaseSQLBuilderImpl.bindParametersForStmt(BaseSQLBuilderImpl.java:3807)
at oracle.jbo.server.ViewObjectImpl.bindParametersForCollection(ViewObjectImpl.java:18278)
at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:1035)
at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:815)
at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:5892)
at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:1021)
at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:889)
…

It is not easy to reproduce but when it happens you cannot open the LOV again and you cannot set a value to the LOV field, even from diferent row or from diferent session.

I managed to reproduce it in a simple test case of Employees form with simple Department LOV.
The steps to reproduce are:

1.Select an existing department

2.open department LOV add a criterion and press search.

3.Close LOV without selecting row and type a non existing value and press Tab. LOV automatically opens and even though it doesnt have values in criteria only the previus results are visible.

4.Press cancel again and type an existing value and press Tab. Then the error apears

It seems that LOVs Love bugs.

LOV view object Tuning: 'Only up to row number' bug (Fixed in 11.1.1.3)

2009-08-04T09:47:00.000-07:00

Since we can not use Range paging on LOVs for performance Tuning due to bug 8722958 :
http://adfbugs.blogspot.com/2009/07/performance-tuning-lovs-and-range.html

I try the 'Only up to row Number' option in a simple employees form with Input List of values for DepartmentId.

so when i open the LOV only 10 rows apear:

Bug1: if i try to type number 110 that is a valid value but does not exist in the range, the value just disapear without even opening the LOV.

Bug2: If i type the number 20 then since both 20 and 200 exist it opens the LOV to select 1. but if i select cancel and after that i type the number 200 the value is set back to 20 and i get a stange error:

Is this a bug?
Or we should not use Tuning: 'Only up to row number' for LOV view objects?

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

Table Validations Bug.

2009-08-03T11:44:00.000-07:00

In a simple Departments Entity i also put 2 transient attributes for this test case reasons.

Then i add some entity and attribute validations.

Then i create a simple ADF Table with submit and commit buttons

I put values in a row so that Entity compare validation should fail. I press submit but nothing happens. I press commit and it seems that data is commited, but they are not!!!

Validation error only shows up if i navigate to an other row by clicking.

but again if i press submit or commit all validation errors disapear!!!?

If i navigate to next row by pressing Tab, again no validation errors!!!

Is this a bug?

Is there any way that these validation errors do not disapear when i press any button?

Test Case:

http://adfbugs.googlecode.com/files/TableValidations.zip

Returning from dialog to a page that has f:verbatim tag bug

2009-08-02T01:43:00.000-07:00

We had a bug in application that when we return from dialog page the page was brocken, bindings were lost, and exceptions apeared in the log.

I managed to reproduce it in a simple test case:
I create a simple page with default oracle template and a dialog page.
I click on header facet and just typed something (test)

I run application i open dialog but when i return from dialog i have exception:

INFO: unable to dispatch JSP page: The following exception occurred:.java.lang.NullPointerException at oracle.adfinternal.view.faces.taglib.region.IncludeTag$RelocatedFacet.restoreFacet(IncludeTag.java:816) at oracle.adfinternal.view.faces.taglib.region.IncludeTag.doStartTag(IncludeTag.java:192) at oracle.adfinternal.view.faces.taglib.region.DynamicIncludeTag.doStartTag(DynamicIncludeTag.java:109) at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:50) at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:257) at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87) at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58) at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:257) at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87) at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58) at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:257) at oracle.jsp.runtime.tree.OracleJspClassicTagNode.evalBody(OracleJspClassicTagNode.java:87) at oracle.jsp.runtime.tree.OracleJspBodyTagNode.executeHandler(OracleJspBodyTagNode.java:58) at oracle.jsp.runtime.tree.OracleJspCustomTagNode.execute(OracleJspCustomTagNode.java:257) at oracle.jsp.runtime.tree.OracleJspNode.execute(OracleJspNode.java:76) at oracle.jsp.runtimev2.ShortCutServlet._jspService(ShortCutServlet.java:88) at oracle.jsp.runtime.OracleJspBase.service(OracleJspBase.java:29) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:416) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:722) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:646) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:500) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:248) at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410) at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44) at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44) at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44) at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267) at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:473) at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:141) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189) at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:685) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:261) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:193) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.wls.util.JpsWlsUtil.runJaasMode(JpsWlsUtil.java:146) at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:159) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

and the page is no longer functional.

If i remove f:verbatim tag the page and dialog work nomraly.

So is this a bug?

If we should not use f:verbatim on ADF pages, why it is set automaticaly when you type something on the page?

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

Range Paging Last operation, bug workaround

2009-08-01T05:48:00.000-07:00

As i posted in previus post when you use Range Paging on a view object then Last operation throws an error.
http://adfbugs.blogspot.com/2009/07/performance-tuning-range-paging-last.html

As Steve suggested i created a method that takes you to the last row:

private Row rangePagingLast() {
int pagesCount = getEstimatedRangePageCount();
scrollToRangePage(pagesCount);
Row lastRow = getRowAtRangeIndex(getRowCountInRange()-1);
setCurrentRow(lastRow);
return lastRow;
}

This method actually gets you to the last row even though Range Paging is set on a view object
It is also much faster than scrolling down to a table component or Last operation of a view object that has Scrolling as Action Mode.
So i overide my base View Object Implementation Class and the Last operation to support Last operation even if Range Paging is set.

@Override
public Row last() {
if (getAccessMode()==ViewObjectImpl.RANGE_PAGING) return rangePagingLast();
return super.last();
}

It seems to work fine.

Test case:

http://adfbugs.googlecode.com/files/TestRangePaging.zip

Range paging and Table Selected Row Bugs

2009-07-30T01:20:00.000-07:00

In a default view object and default table in panel collection, when you scroll down and select a row and for any reason the table is submitted (button, reorder columns, detach), then the table returns to the first displayed page and the selected row was not visible.
But you could fix that if in the table properties you set displayRow="selected".
Except form the detach button that still reset the visible range to the start.

Bug1 :Yet when you set Range paging for tuning the view object the displayed (selected) row is lost many times (not always) when you submit page.

Bug2 :Also some times the selection listener of the table does not work and when you submit the previus selected row is selected

Bug3 : Last it seams that it execute many ranges in the query, not only when you scroll down, but also when you select a row.

So is this a bug?
or we should not use Range Paging in view objects used in table?

Test Case:

http://adfbugs.googlecode.com/files/TestRangePaging.zip

Iterating through View Object RowIterator Bug.(NOT ADF BUG, Development Bug)

2009-07-28T12:49:00.000-07:00

The oldest bug in writing code is losing a row in an iterator.
This happens in ADF also.
I got embarrassed today saying to a developer 'RTFM' and been proven wrong. So I will first post some parts of the javadoc of RowIterrator and then a test case that proves it wrong.

When a Row Iterator is first opened or created, the currency is placed on an imaginary "slot" before the first row. This enables the user to invoke next() on a fresh new Row Iterator and retrieve the first row. For example, the following block of code will print attribute "Ename" for all employees (it does not miss the first row):
ApplicationModule myAM;
...
ViewObject myVO = myAM.findViewObject("MyEmpVO");
Row row;
while ((row = myVO.next()) != null)
{
System.out.println("Ename: " + row.getAttribute("Ename"));
}

void reset()
Moves the currency to the slot before the first row.
After this method, the current slot status will be SLOT_BEFORE_FIRST except in cases where this iterator is associated to an iterator binding in an ADF application which sets the currency to the first row in the iterator if available. A subsequent invocation of next() will cause the first row to become the current row.

So I created a View Object that only gets 3 rows and a method in application module that iterrates according to the above descriptions through the iterator and return the rows visited in a string:
public String checkIterations() {
String res = "Iterated through : ";
RowIterator view = this.getDepartmentsView1();
view.reset();
Row row;
while ((row = view.next()) != null) {
System.out.println("rownum: " + row.getAttribute("RowNum"));
res += row.getAttribute("RowNum") + " ";
}
return res;
}
When I run Application nodule and test this method, it goes through all rows as expected.

But if I open the view object (execute query) and then run this method again, the first row is never visited.

So is this a bug?

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

As my friends in the comments said its not a bug
Its a bad development practice (development bug) to do it as described above.

I should say RATFM (readh all the f... manual):

9.7.6 What You May Need to Know About Programmatic Row Set Iteration

Any time your application logic accesses a row set to perform programmatic iteration, you should use a secondary row set iterator when working with view object instances in an application module's data model, or view link accessor row sets of these view object instances, since they may be bound to user interface components.
To create a secondary iterator, use the createRowSetIterator() method on the row set you are working with. When you are done using it, call the closeRowSetIterator() method on the row set to remove the secondary iterator from memory.
Example 9-7 shows a typical application module custom method that correctly uses a secondary row set iterator for programmatic iteration, because the EmpView1 view object instance in its data model may be bound to a user interface (either now or at a later time).
Example 9-7 Using a Secondary Row Set Iterator in an Application Module Custom Method
// Custom method in an application module implementation classpublic
void doSomeCustomProcessing() {
ViewObject vo = getEmpView1();
// create secondary row set iterator with system-assigned name
RowSetIterator iter = vo.createRowSetIterator(null);
while (iter.hasNext()) {
Row r = iter.next();
// Do something with the current row.
}
// close secondary row set iterator
iter.closeRowSetIterator();}