This content has been marked as final. Show 3 replies
as you got a NPE at
means that at the time you run this code there is no current row defined for the 'Empmaster1Iterator'.
String fName = (String)currentRow.getAttribute("FirstName");
The question now is why don't you have a current row?
One reason can be that the iterator simply doesn't have a row. With the information provided we can only guess. However, you should check if you get a row before using the row. If you get null you have to decide what to do,
That makes sense Timo.
My problem is that when I query the database outside of JDev I have the row, when I run the app in the Integrated WLS I have the row, when I run the app on the production WLS, I get NPE.
And no doubt I can handle the NPE, by returning a dialog message. But, that doesn't identify why this is happening.
Knowing that the record exists in the database, what is my next course of action?
Thanks for all your help Timo.
After digging further, I found another message that was somehow suppressed by the NPE message.
ORA-01005: null password given; logon denied
After that, it all fell into place.
I changed my AM >> Configurations >> Edit from JDBC URL to JDBC Datasource.