@Maxim: I don't think that "Collections" in general are an issue Try for example: http://demo.openmeetings.de/openmeetings/services/RoomService/getFlvRecordingByExternalRoomTypeByList?SID=XXXXXXX&externalRoomType=moodle
with a valid SID. You will get this result: http://pastebin.com/aggRm3uH so the return type: java.util.List<FlvRecording> ist working fine. What I get when I run: demo.openmeetings.de/openmeetings/services/RoomService/getRooms?SID=xxxxxxx&start=0&max=10&orderby=c.rooms&asc=true is: org.apache.axis2.AxisFault: Mapping qname not fond for the package: org.openmeetings.app.data.beans.basic => I think Axis2 has an issue with Typed-Parameters. Looking at the: http://demo.openmeetings.de/openmeetings/services/RoomService?wsdl I cannot find a mapping for "SearchResult" We had the same issue some time ago with deeply nested objects in Axis2. Updating Axis2 to SNAPSHOT did help: http://mail-archives.apache.org/mod_mbox/axis-java-user/201203.mbox/%3ccanzufzfjhvkjzaunmot9f-utm+efbjhkbai369oaxh8hjvi...@mail.gmail.com%3E However as there is no more recent version then Axis2 "SNAPSHOT" ... :)) so... I don't know what we should do with this API call atm. @Ankur: You shouldn't use the "getRooms" API call at all. You should use this call: http://incubator.apache.org/openmeetings/RoomService.html#getRoomsWithCurrentUsersByListAndType You only want to list those rooms that you have created via Zimbra not "globally all". So to get only rooms created by zimbra you create the room with the API call: http://incubator.apache.org/openmeetings/RoomService.html#addRoomWithModerationAndExternalType and with the param: externalRoomType=zimbra123 and when you want to list all rooms created in Zimbra you use: http://incubator.apache.org/openmeetings/RoomService.html#getRoomsWithCurrentUsersByListAndType with parameter externalRoomType=zimbra123 => That way you filter the results by "zimbra123" and the Zimbra user does not see rooms of other integrations or that are created via OpenMeetings standalone The parameter "externalRoomType" is normally a parameter that you would specify together with the API settings like "openmeetings API user" ... that way several Zimbra integrations can use the same OpenMeetings user => Just by using different "externalRoomType". The API Call: http://incubator.apache.org/openmeetings/RoomService.html#addRoomWithModerationAndExternalType => Already has a "Axis2 safe" return type ok? 2012/6/29 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > While investigating this issue I found the following additional problem: > Axis is not supports returning java collections as a result. > i.e. all our axis services should not return java.util.List etc. > > As side effect returning of SearchResult is not allowed. > Should I fix this? > > Is it OK to create AxisSerchResult having result as array instead of List? > > > On Fri, Jun 29, 2012 at 5:35 PM, Maxim Solodovnik <[email protected]>wrote: > >> I can confirm this. >> I'll fix it today and let you know >> >> >> On Fri, Jun 29, 2012 at 5:33 PM, Maxim Solodovnik >> <[email protected]>wrote: >> >>> I'll check >>> >>> >>> On Fri, Jun 29, 2012 at 5:32 PM, Ankur Ankan <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> After logging in when I send the getRooms request: >>>> >>>> >>>> http://demo.dataved.ru/openmeetings/services/RoomService/getRooms?SID=55bc3c4bb04c9f7eff1aa76ef5c26185&start=2&max=25&orderby=name&asc=0 >>>> >>>> It returns: >>>> >>>> <soapenv:Reason xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope >>>> "> >>>> <soapenv:Text xml:lang="en-US"> >>>> Failed to execute query "select c from Rooms c where c.deleted <> 'true' >>>> AND c.name LIKE :search ORDER BY name DESC". Check the query syntax for >>>> correctness. See nested exception for details.; nested exception is >>>> <openjpa-2.2.0-r422266:1244990 nonfatal user error> >>>> org.apache.openjpa.persistence.ArgumentException: Failed to execute >>>> query >>>> "select c from Rooms c where c.deleted <> 'true' AND c.name LIKE >>>> :search >>>> ORDER BY name DESC". Check the query syntax for correctness. See nested >>>> exception for details. >>>> </soapenv:Text> >>>> </soapenv:Reason> >>>> >>>> >>>> Is the request correct and if it is correct what is the problem?? >>>> >>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
