> Building the rpcexample shows the follwing errors: Unknown gobal symbol > referenced: > > ============================================================================ > EXECUTING: BUILD::BUILD-SCRIPT > ============================================================================ >>>> Initializing cache... >>>> Scanning libraries... >>>> Resolving dependencies... > *- ! Unknown global symbol referenced: t0 (rpcexample.Application:354)* > * - ! Unknown global symbol referenced: i (rpcexample.Application:362)* > * - ! Unknown global symbol referenced: t (rpcexample.Application:370)* > * - ! Unknown global symbol referenced: seqnum > (rpcexample.Application:389)* > * - ! Unknown global symbol referenced: obj (rpcexample.Application:552)* > * - ! Unknown global symbol referenced: obj.s (rpcexample.Application:553)* > * - ! Unknown global symbol referenced: obj.n (rpcexample.Application:554)* > * - ! Unknown global symbol referenced: obj.o (rpcexample.Application:555)* > * - ! Unknown global symbol referenced: obj.o.s > (rpcexample.Application:556)* > * - ! Unknown global symbol referenced: rpc (rpcexample.Application:713)* > * - ! Unknown global symbol referenced: handler > (rpcexample.Application:713)* > * - ! Unknown global symbol referenced: handler > (rpcexample.RemoteDataModel:55)* > * - ! Unknown global symbol referenced: mycall > (rpcexample.RemoteDataModel:57)*
These are not errors, but warnings, and they are all justified, as the code contains exactly these global symbols (as you can easily see looking at it). But these global symbols are not impeding the application at all (at worst, they pollute the global name space), so you can safely ignore them. > The Browser alerts with: > *Async(null) exception: Application error 0: Services require > JSON-RPC<p>Are you sure you configured rpcexample.RemoteDataModel.URL > and rpcexample.RemoteDataModel.SERVICE?* Well, did you? > > Then when I am sending a message the rpc-server responds with: > *Sync exception: Error: Application error 0: Services require JSON-RPC* Maybe a follow-up error of the previous. > I do not have the time to search for hours. Now I passed 2 days with the > basics of qooxdoo but did not succeed. I presume you managed to get a gui skeleton running (which I would consider 'basic'). Getting RPC to work is more involved, as you can see when you search the mailing list. Which RPC server are you running against? The RpcExample contrib declares it is compatible with qooxdoo 0.7 and 0.8, but you are probably running a qooxdoo higher than that?! As an alternative, you might consider trying the RpcConsole contribution, which is tested on more recent qooxdoo versions. - Maybe Derrell can comment on RpcExample. T. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
