jaleman wrote:Can you try adding a loadAllRecords before you create?
The newRecord method is now:
- Code: Select all
controller.loadAllRecords();
controller.newRecord();
controller.saveData();
return 'ok';
I run the JSP. Session is launched, OK is returned, no new record is created.
In the hope of getting more info on what's going on I now revise newRecord to:
- Code: Select all
controller.loadAllRecords();
var vSize1 = foundset.getSize();
return vSize1;
controller.newRecord();
controller.saveData();
var vSize2 = foundset.getSize();
return vSize2;
return 'ok';
I restart the server and then re-run the JSP. Instead of saying OK, the web page now reports
Access is denied or Error occurred:
The server log was checked before running the JSP and I've checked it again (clicking Refresh) after the JSP run. It remains unchanged before and after:
2006-06-30 13:29 : Loading servoy.properties from /Applications/Servoy/servoy.properties
2006-06-30 13:29 : Loading - Done
2006-06-30 13:30 : Using RMI registry on port 1099
2006-06-30 13:31 : Error occured informing client plugin udp, error: java.lang.NullPointerException
====
I've been getting that mysterious client plugin udp error message erratically throughout my recent attempts to get newClient to function. For instance, earlier today I uploaded a new version of newClient (with your recommended addition to the newRecord method) and then restarted the server (in order to flush anything left over from the previous run).
The log now presented me with:
2006-06-30 12:55 : Loading servoy.properties from /Applications/Servoy/servoy.properties
2006-06-30 12:55 : Loading - Done
2006-06-30 12:55 : Using RMI registry on port 1099
2006-06-30 12:55 : Error occured informing client plugin udp, error: java.lang.NullPointerException
This is
before running the JSP or doing anything.
Given the fact this error turns up when just uploading a new version of the newClient solution and doing nothing else I'm assuming this error has nothing to do with the failure of the newRecord method.
Earlier today I checked Batch Processors to see what might be running there. I found two, the solution called dailyUpdate.servoy (which launches some chrons to massage the database daily). That's been in place for some time and has always worked flawlessly without error messages. The second one was newClient (which does nothing but wait for a JSP to send it instructions.)
As I write this report following the two experiments reported above I can see there are two clients running -- dailyUpdate and newClient. But if I go to Batch Proessors dailyUpdate is running and newClient is
not running. Not sure of the significance, if any.
I mention all this in an effort to be thorough in reporting. Let me know if this helps in understanding what's going on here.
Cheers,