This content has been marked as final. Show 4 replies
Hi,1 person found this helpful
Row currentRow = addrDetailViewObj.getCurrentRow();
if noone selected a current row on the UI. If you don't call this then actually no row is current
Thanks for the quick response. I will try your solution, I just wanted to know During Pooling OFF - why does it behave like that? However during Pooling ON it is working fine without any issues.
I found this exception even in other App Module as well where we have ViewLink. For the regular View Object (no master/child relationship) it works fine with Pooling OFF.
Edited by: user5396188 on Feb 28, 2012 2:57 AM
Edited by: user5396188 on Feb 28, 2012 2:58 AM
When you work with am pooling off, the state of the am should be written into the db (ps_txn). However, there are some states (like the current row) which is not written into the db (in some versions of jdev). So when the am gets activated there is no current row and you get a NPE in your code (addrDetailViewObj.getCurrentRow();).
The only workaround I know is to store the key of the current row when you get passivated and when you get activated set it again.
Check http://tompeez.wordpress.com/2011/07/08/jdev-always-test-your-app-with-applicationmodule-pooling-turned-off/ for more info.
Thanks Timo. I viewed the link however I do not have any session specific user data used by either ViewLink or our Application Code. Also the relationship between source and destination viewobjects in ViewLink is static and there is no dynamic bind variable being passed.
I just wanted to know is there any limitation in Oracle ADF for ViewLink while Activation and Passivation? We are using Oracle ADF JDev 220.127.116.11.0
Edited by: user5396188 on Feb 28, 2012 10:14 PM