There seems to be some sort of incompatibility with some LOVs when I enable Disconnect Application Module Upon Release.
I have an LOV based on an updatable VO with a bind parameter.
When I first log on the application an try to use the LOV I get a NPE when I select the row from the LOV popup and press OK.
If I navigate to another page and return the LOV starts working correctly
The NPE occurs in line
getIterBinding().getCurrentRow() is null it this case.
Do you have any hints?
public void copyReturnValues(Map selectedRowData, Row baseRow, boolean copyToUI, boolean commaSeparated)
// first clear any dependent items, if they exist
if (getTableBean() != null)
List keyList = new ArrayList();
I was using Disconnect Application Module Upon Release to overcome an issue I had with multiple duplicated rows being generated in a table under certain circumstances.
What I had is a button which reads the rows of a table and creates new rows in another table (other viewobject) which have a foreign key to the rows of the first table.
If I issue multiple requests on the first table (5rows) by clicking different rows very fast and at the same time I press the button to create new rows to the second table the results are undefined. Instead of getting 5 new rows I get 10 or even 15 or 20. I don't know if this is a bug or if I am doing something wrong but I managed to overcome this by using the Entity RowSet instead of the ViewObject RowSet.
so now I am not using Disconnect Application Module Upon Release any more.