Hi Derrell,
Derrell Lipman wrote: > > If you can run RpcExample, all tabs, using your server and an > *unaltered*test.php and remoteTableTest.php > *copied from 1.0.0*, then you've likely got a properly working server. In > particular, the third and fourth tabs, the sync and async tests, run > through > each of the primitive functional capabilities I believe. You do need to > look > at the output in the debug console to ensure you're getting proper > results. > If the test runs to completion, you'll get an exception for the getError() > call that references an *application* error (42, I think) if it worked > properly. Note also that getError() is called twice. The first time, the > $error return value is used; the second time, a new JsonRpcError is > thrown. > You should get the same alert at the browser for each of them. > > I think I fixed all issues with the trunk version of RpcPhp to make it compatible with your excellent test suite for the jsonrpc server backend. At the moment, I cannot commit to the sourceforge svn (see my other message) but I hope it will be possible soon. I attach two patches (in Nabble) with proposed changes to RpcExample and the test.php: 1) http://www.nabble.com/file/p24119600/Patch-RpcExample.txt Patch-RpcExample.txt : I think it is not very convenient to have to change the javascript source code of the RpcExample just to change the URL of the server and to have to paste the server URL in each of the test tabs of the application. I propose to use a setting that can be changed in the config.json and which will be automatically inserted in the URL textfields in the tabs. 2) http://www.nabble.com/file/p24119600/Patch-test.php.txt Patch-test.php.txt : I try to keep at least the next stable release of the server backwards-compatible with PHP4. So I propose to change a line in test.php so that the file is parsed without error. I have rewritten the JsonRpcServer class to be PHP4/PHP5 compatible, so that the JsonRpcServerPhp5 class is now no longer necessary and will be removed from the trunk. There was one small thing in that the application says that the number of the last error generated was supposed to be "1000", but it alerted "23", so I changed that in test.php. With PHP5, I could run all tests sucessfully, in PHP4, the Date()-related stuff failed, but that should be ok for the moment. Finally, I first tried RpcExample with qooxdoo-trunk, which did not work, so there might be some work ahead to update it. Thanks, Christian -- View this message in context: http://www.nabble.com/RPC-Server%3A-JsonRpcError%28%29-tp24093948p24119600.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
