Same exact response from it even if I corrupt the session id. Restarted the service, then rebooted the server and same thing after both events. Starting to think I might have something corrupted from install.
However, I can get an "unknown" response if I leave rooms_id as blank. Would the cache be able to stay between reboots? If so, is there a way to manually clear it out/force it to refresh? On Sun, Jun 9, 2013 at 10:47 AM, Maxim Solodovnik <[email protected]>wrote: > Weird, I have just checked it. > Works as expected. Maybe somehow cache issue? > On Jun 9, 2013 9:11 PM, "John Doe" <[email protected]> wrote: > >> That is the current setup I have running, getSession returns a SID, >> loginUser returns "1", and then no matter what room_id I send to >> getRoomsById it returns the same XML response. >> >> . >> >> >> On Sun, Jun 9, 2013 at 6:57 AM, Maxim Solodovnik <[email protected]>wrote: >> >>> you should call: >>> 1) services/UserService/getSession >>> >>> 2) >>> services/UserService/loginUser?SID=SID_FROM_POINT_1&username=USERNAME&userpass=PASSWORD >>> 3) services/RoomService/getRoomById?SID=SID_FROM_POINT_1&rooms_id=1 >>> >>> >>> >>> On Sat, Jun 8, 2013 at 8:54 PM, John Doe <[email protected]>wrote: >>> >>>> When using the getRoomById API call, which room_id is it looking for. >>>> I have tried calling to for an ID I know is good and one that is not used, >>>> but I get the same XML response from both. >>>> >>>> ... >>>> openmeetings/services/RoomService/getRoomById?SID=26d03a64e097b4e2f64ff8a089ad8229&rooms_id=1 >>>> >>>> and ... >>>> openmeetings/services/RoomService/getRoomById?SID=26d03a64e097b4e2f64ff8a089ad8229&rooms_id=99 >>>> >>>> The response from both is: >>>> >>>> <ns:getRoomByIdResponse xmlns:ns=" >>>> http://services.axis.openmeetings.apache.org";><ns:return xmlns:xsi=" >>>> http://www.w3.org/2001/XMLSchema-instance"; >>>> xsi:nil="true"/></ns:getRoomByIdResponse> >>>> >>>> What I am trying to do is confirm that a room exists. Am I formatting >>>> the call incorrectly or should I be using a different call? >>>> >>>> Before this I am able to confirm the session id was generated and it >>>> accepted the login. >>>> >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >>
