[
https://issues.apache.org/jira/browse/OPENMEETINGS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861192#comment-13861192
]
Yannick Warnier commented on OPENMEETINGS-802:
----------------------------------------------
I'm definitely having issues with the REST services. At the same time, I saw
this e-mail from a year ago that suggests to someone to try
JabberService::getAvailableRooms instead of
RoomService::getRoomsWithCurrentUsersByListAndType. Is there any useful reason
behind that?
At the moment, I'm doing this:
http://video.com:5080/openmeetings/services/RoomService/getRoomsWithCurrentUsersByListAndType?SID=e380f65990f770d28ed5f424b38f7be7&start=1&max=1000&orderby=name&asc=true&externalRoomType=chamilolms
Which says: Your call to OpenMeetings Web Services returned an unexpected HTTP
status of: 500
And I get no result (but I don't know if that's because there are no results
for this particular type, or if that's because it fails). Analysing the XML
response, I get:
{code}
<soapenv:Reason><soapenv:Text
xml:lang="en-US">unknown</soapenv:Text></soapenv:Reason>
{/code}
When I try:
http://video.com:5080/openmeetings/services/JabberService/getAvailableRooms?SID=e380f65990f770d28ed5f424b38f7be7
(same SID, as you can see) then I get several rooms details as a result. The
XML response is obviously much more complete.
I don't get the idea of why one webservice
> Integration with Chamilo LMS
> ----------------------------
>
> Key: OPENMEETINGS-802
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-802
> Project: Openmeetings
> Issue Type: New Feature
> Components: SOAP/REST API
> Reporter: Yannick Warnier
> Priority: Trivial
> Labels: plugin
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We (at Chamilo/BeezNest) are currently developing a first plugin for
> OpenMeetings, to be integrated to Chamilo LMS 1.9.8.
> This is just a placeholder so nobody has to dedicate time on this at the same
> time (or if you do, let me know so I can add you to the team).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)