Earlier this year

• Oct 22, 2009

  issue 42 (Compatibility issues with mysqlpp version 3.09) commented on by joel.granados   -   markushx What did your patch look like? I have a patch that gets the source compiled but did not run any tests on it (I'll post my patch). How did you solve that issue? From a dude that might be interested in working with this. Regards.

  markushx What did your patch look like? I have a patch that gets the source compiled but did not run any tests on it (I'll post my patch). How did you solve that issue? From a dude that might be interested in working with this. Regards.
• Jun 15, 2009

  issue 42 (Compatibility issues with mysqlpp version 3.09) changed by jonas.fonseca   -   No, there is no such effort. I assume you have looked at: http://tangentsoft.org/mysql++/doc/html/userman/breakages.html#api-3.0.0 As part of my thesis I moved much of the code to a single (Maven-based) repository of which you can find a snapshot at http://testbed.ekstranet.diku.dk/pub/download/remote/. I also started to port part of the MCI code namely the mote control server to Java, but didn't get very far. However, in the long run I think that is a better solution since it will make all the server code more easily deployable.

  Summary: Compatibility issues with mysqlpp version 3.09

  Labels: Component-MCI

  No, there is no such effort. I assume you have looked at: http://tangentsoft.org/mysql++/doc/html/userman/breakages.html#api-3.0.0 As part of my thesis I moved much of the code to a single (Maven-based) repository of which you can find a snapshot at http://testbed.ekstranet.diku.dk/pub/download/remote/. I also started to port part of the MCI code namely the mote control server to Java, but didn't get very far. However, in the long run I think that is a better solution since it will make all the server code more easily deployable.

  Summary: Compatibility issues with mysqlpp version 3.09

  Labels: Component-MCI
• Jun 11, 2009

  issue 42 (Compatability issues with mysqlpp 3.09) reported by markushx   -   We are trying to get ReMote up and running. We are struggling because the mysqlpp interface has changed considerably from mysqlpp 2 to 3. Unfortunately mysqlpp 2 is not available in Debian anymore, so we were trying to go with mysqlpp 3.09. In Host.cc we made several changes: * UseQueryResult instead of ResUse * SimpleResult instead of ResNSel We needed to uncomment some purge(), however now we get: "terminate called after throwing an instance of 'mysqlpp::BadQuery' what(): Commands out of sync; you can't run this command now Aborted" Are there efforts to move to mysqlpp 3.09? Do you have any suggestions? Thanks, Markus

  We are trying to get ReMote up and running. We are struggling because the mysqlpp interface has changed considerably from mysqlpp 2 to 3. Unfortunately mysqlpp 2 is not available in Debian anymore, so we were trying to go with mysqlpp 3.09. In Host.cc we made several changes: * UseQueryResult instead of ResUse * SimpleResult instead of ResNSel We needed to uncomment some purge(), however now we get: "terminate called after throwing an instance of 'mysqlpp::BadQuery' what(): Commands out of sync; you can't run this command now Aborted" Are there efforts to move to mysqlpp 3.09? Do you have any suggestions? Thanks, Markus
• Mar 17, 2009

  AdministratorManual (How to install and maintain a testbeds with Re-Mote) Wiki page edited by jonas.fonseca
• Mar 09, 2009

  RoadMap (Development roadmap and release plans) Wiki page edited by jonas.fonseca
• Mar 09, 2009

  issue 34 (Move to JAX-WS as the platform for client RPC) Summary changed by jonas.fonseca   -   Change from Axis 2 to JAX-WS.

  Summary: Move to JAX-WS as the platform for client RPC

  Change from Axis 2 to JAX-WS.

  Summary: Move to JAX-WS as the platform for client RPC
• Jan 13, 2009

  UserManual (Manual for using the Re-Mote client) Wiki page edited by jonas.fonseca
• Jan 13, 2009

  AdministratorManual (How to install and maintain a testbeds with Re-Mote) Wiki page edited by jonas.fonseca