I need help from community to document this
I have no time to write code otherwise :((((

Additionally I was thinking about add Swanger to REST ....

On Fri, Aug 19, 2016 at 8:23 AM, Maxim Solodovnik <solomax...@gmail.com>
wrote:

> Actually everything was changed
>
> 0) Axis was removed in favor of CXF
> 1) services were split to multiple groups error, user, group, room
> recording etc.
> 2) method signatures were cleaned up
> 3) REST methods are works with JSON now (and produces both XML and JSON)
> 4) REST methods uses GET/POST/DELETE (I haven't added PUT)
>
>
> On Fri, Aug 19, 2016 at 8:16 AM, seba.wag...@gmail.com <
> seba.wag...@gmail.com> wrote:
>
>> Has it been reworked to fit into the REST (GET/PUT/POST/DELETE)
>> specification? Is that the change?
>>
>> Cause AFAIK I think the methods/flow are the same, right ?
>>
>> Thanks,
>> Sebastian
>>
>> 2016-08-19 11:09 GMT+10:00 Maxim Solodovnik <solomax...@gmail.com>:
>>
>>> Hello,
>>>
>>> The API was changed (it was discussed here: http://openmeetings.mark
>>> mail.org/thread/43d5irskmknn3u6u)
>>> Full API as javadocs available here http://openmeetings.apach
>>> e.org/openmeetings-webservice/apidocs/index.html
>>> Short example available here: http://openmeetings.apac
>>> he.org/RestAPISample.html
>>> PHP API is here: https://github.com/openmeetings/openmeetings-api-plugin
>>>
>>> unfortunately there no t much documentation :(
>>> I have filed issue against this: https://issues.apache.or
>>> g/jira/browse/OPENMEETINGS-1451
>>>
>>> suggestions/contributions are welcome :)
>>>
>>> On Fri, Aug 19, 2016 at 2:45 AM, Bhushan Patil <
>>> thebhushanpa...@gmail.com> wrote:
>>>
>>>> Hello everyone, we have integrated older version of Openmeetings with
>>>> our application. At the time of migration to OM 3.1.2, we realized that api
>>>> are changed. We want to  keep old code as well as write new code for newer
>>>> APIs.
>>>> I am unable to find soap/rest api which let us know version of
>>>> Openmeetings.
>>>> Any suggestions?
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> seba.wag...@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
WBR
Maxim aka solomax

Reply via email to