Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

da4e8828-743d-4968-af6f-49033f10d60a/public_url> >> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >> >> >> On Fri, 24 Sept 2021 at 09:20, seba.wag...@gmail.com < >> seba.wag...@gmail.com> wrote: >> >>>

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

On Fri, 24 Sept 2021 at 09:20, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> *So far I don't see how the existence of SOAP complicates things :)* >> >> => See below list of what a potential v2 of the Rest API could/should >> fix. I don't see

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

> *So far I don't see how the existence of SOAP complicates things :)* > > => See below list of what a potential v2 of the Rest API could/should fix. > I don't see how this can be fixed while keeping SOAP and REST in the same > class definition: > > *Security - 2.4. Never

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

> > *So far I don't see how the existence of SOAP complicates things :)* => See below list of what a potential v2 of the Rest API could/should fix. I don't see how this can be fixed while keeping SOAP and REST in the same class definition: *Security - 2.4. Never expose sensitive in

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

> So far I don't see how the existence of SOAP complicates things :) > *We introduced REST 10years ago and the definitions of REST changed over > time* > => We created the OpenMeetings REST API over 10years(!!) ago. At that time > the definition of REST was quite fluent. By now t

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

ver time it actually became harder, cause we discovered that under the covers Soap and Rest representation is different. *We introduced REST 10years ago and the definitions of REST changed over time* => We created the OpenMeetings REST API over 10years(!!) ago. At that time the definition o

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

both* => It was easy when the API was simple. But then over time it actually became harder, cause we discovered that under the covers Soap and Rest representation is different. *We introduced REST 10years ago and the definitions of REST changed over time* => We created the OpenMeetings REST AP

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

everal years :))) What is several years ;-) Well I believe REST API was changed 2-3 times, so we are trying to keep it stable v1/v2 etc. approach can also be applied the problem here: I don't have enough time to maintain more than one version :(( On Wed, 22 Sept 2021 at 19:0

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

hanges now and let the API unchanged for another several years :))) What is several years ;-) Well I believe REST API was changed 2-3 times, so we are trying to keep it stable v1/v2 etc. approach can also be applied the problem here: I don't have enough time to maintain more than one v

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

will be able to do them) worth to be done > > what is IMO ? > In My Opinion :) > Why I raise some old design issues: we can do changes now and let the API > unchanged for another several years :))) > > What is several years ;-) > Well I believe REST API was changed 2-3 tim

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

b4f05f4f#comments <https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments> we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Problem: JSO

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

t; Video-Conferencing OpenMeetings >>> >>> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> >>> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >>> >>> >>> On Wed,

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

mit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments <https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments> we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Proble

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

;https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >> >> >> On Wed, 22 Sept 2021 at 10:59, Ali Alhaidary >> wrote: >> >>> Hi, >>> >>> We have an old saying 'If it is not broken, do not fix it' ;-) >

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

hing in our API >> >> Maybe you can point to some others :) >> >> >>> >>> Thanks >>> Seb >>> >>> >>> Sebastian Wagner >>> Director Arrakeen Solutions, OM-Hosting.com >>> http://arrakeen-solutions.co.nz/ >>>

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

//github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments> we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Problem: JSON response wrapping Currently CXF-RS is configured to wrap th

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

rote: >> >> Hi, >> >> as discussed in the comments section in >> https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments >> >> >> we would like to propose a breaking change for the OpenMeetings Json/Rest >> API in v7.

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

gt; >> <https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url> >> <https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> >> >> >> On Wed, 22 Sept 2021 at 17:19, Maxim Solodovnik >> wrote: >> >>

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments <https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments> we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Problem: JSON response wrapp

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

ps://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url> > > > On Wed, 22 Sept 2021 at 17:19, Maxim Solodovnik > wrote: > >> I'm +1 for the change :) >> >> And I propose to check the current REST API to be clearer >&g

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

> On Wed, 22 Sept 2021 at 17:19, Maxim Solodovnik wrote: > I'm +1 for the change :) > > And I propose to check the current REST API to be clearer > for ex. right now we have `JSON.stringify` [1] in some places, and NOT in > some others > I would completely get rid of i

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

I'm +1 for the change :) And I propose to check the current REST API to be clearer for ex. right now we have `JSON.stringify` [1] in some places, and NOT in some others I would completely get rid of it :( this particular change is small and will affect 1-2 lines of code in Moodle plugin :) [1

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

21 12:46 AM, seba.wag...@gmail.com wrote: > > Hi, > > as discussed in the comments section in > https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments > > > we would like to propose a breaking change for the OpenMeetings Json/Rest >

Re: [DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

che/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments> we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Problem: JSON response wrapping Currently CXF-RS is configured to wrap the JSON response into another object. Example:

[DISCUSS] Breaking JSON response body change in OpenMeetings Json/Rest API 7.0.0

Hi, as discussed in the comments section in https://github.com/apache/openmeetings/commit/4daf7c1f53738cd786dc976114cc5278b4f05f4f#comments we would like to propose a breaking change for the OpenMeetings Json/Rest API in v7.0.0 Problem: JSON response wrapping Currently CXF-RS is configured

Re: REST API to upload file

I cannot find a search function. Am Mi., 29. Apr. 2020 um 07:42 Uhr schrieb Maxim Solodovnik < solomax...@gmail.com>: > ML == mailing lists > https://openmeetings.apache.org/mailing-lists.html > > On Wed, 29 Apr 2020 at 12:41, K. Kamhamea wrote: > > > > Waht is " ML archives " ? > > > > Am Mi.,

Re: REST API to upload file

This is headers and body of sending a one pixel transparent png image that triggers an 415 response. 'body': b'--668f009a1a08af558360542449ab33d1\r\nContent-Disposition: form-da' b'ta; name="file"\r\n\r\n{"ownerId": 12, "name": "spacer.png", "ro' b'omId": 50, "externalType":

Re: REST API to upload file

ML == mailing lists https://openmeetings.apache.org/mailing-lists.html On Wed, 29 Apr 2020 at 12:41, K. Kamhamea wrote: > > Waht is " ML archives " ? > > Am Mi., 29. Apr. 2020 um 03:47 Uhr schrieb Maxim Solodovnik > : >> >> On Tue, 28 Apr 2020 at 23:20, K. Kamhamea wrote: >> > >> > Does the

Re: REST API to upload file

Waht is " ML archives " ? Am Mi., 29. Apr. 2020 um 03:47 Uhr schrieb Maxim Solodovnik < solomax...@gmail.com>: > On Tue, 28 Apr 2020 at 23:20, K. Kamhamea wrote: > > > > Does the file upload with moodle really work? I doubt so, as header and > body in my requests look almost the same no matter

Re: REST API to upload file

On Tue, 28 Apr 2020 at 23:20, K. Kamhamea wrote: > > Does the file upload with moodle really work? I doubt so, as header and body > in my requests look almost the same no matter which software I use to > generate it. Yes > > Is it possible that it depends on the content of the fileDTO? What

Re: REST API to upload file

Does the file upload with moodle really work? I doubt so, as header and body in my requests look almost the same no matter which software I use to generate it. Is it possible that it depends on the content of the fileDTO? What fields are required in that structure. Also can I turn some debug on,

Re: REST API to upload file

Please check sources for moodle plugin On Tue, Apr 28, 2020, 19:06 K. Kamhamea wrote: > Has anyone successfully used file upload with WebServices. I always get an > HTTP 415 error. > And of course I used headers > > 'Content-type': "multipart/form-data" > > > There is a discrepancy in the

Re: Verbose logging for SOAP and REST API calls

well REST/SOAP is made by CXF so you should specify "org.apache.cxf" as logger name the most detailed level is TRACE (but this might be too much ...) On Mon, 30 Mar 2020 at 21:04, Daniel Baker wrote: > Hi Maxim , > > How can I enable a more verbose logging . > > Would this work for us too :

Verbose logging for SOAP and REST API calls

Hi Maxim , How can I enable a  more  verbose  logging . Would this work for us  too : "To make logging more verbose you can 1. stop OM 2. add following line to logback-config.xml 3) restart OM  " Thanks, Dan

Re: REST API parameter to load to Whiteboard

Hello Daniel, there is no such API ATM On Fri, 6 Mar 2020 at 22:41, Daniel Baker wrote: > > Hi Maxim, > > > We got the rest API to load files to the room however we are not > sure what we have to configure to make it load to the whiteboard. It > currently l

REST API parameter to load to Whiteboard

Hi Maxim, We  got the rest  API to load  files  to the  room  however  we are  not sure  what  we have to configure to make it load  to the whiteboard.  It currently loads to the file tree. Can you point me to the necessary  parameter in the moodle OM api  as  an example. Thanks, Dan

Re: REST API : Profile Picture URL

OK. I'll re-install using MariaDB. I probably made a mistake during install. Thank you VERY MUCH, Maxim Le 15/08/2017 à 10:02, Maxim Solodovnik a écrit : AFAIK there is no chance to query Derby DB On Tue, Aug 15, 2017 at 3:01 PM, Jacob Ouanounou wrote: In persistence.xml I

Re: REST API : Profile Picture URL

AFAIK there is no chance to query Derby DB On Tue, Aug 15, 2017 at 3:01 PM, Jacob Ouanounou wrote: > In persistence.xml I find this : > > value="DriverClassName=org.apache.derby.jdbc.EmbeddedDriver,Url=jdbc:derby:open330;create=true, > ... > > which I assume means that I am

Re: REST API : Profile Picture URL

In persistence.xml I find this : value="DriverClassName=org.apache.derby.jdbc.EmbeddedDriver,Url=jdbc:derby:open330;create=true, ... which I assume means that I am using derby. How can I access and make a query on Derby ? Le 15/08/2017 à 05:23, Maxim Solodovnik a écrit : please find

Re: REST API : Profile Picture URL

please find persistense.xml and check what DB driver is used On Mon, Aug 14, 2017 at 10:59 PM, Jacob Ouanounou wrote: > I thought that I had configured OM to use MariaDB, but the database is > empty. Would it mean that it uses Derby ? How can I check ? > > > Le 11/08/2017 à

Re: REST API : Profile Picture URL

I thought that I had configured OM to use MariaDB, but the database is empty. Would it mean that it uses Derby ? How can I check ? Le 11/08/2017 à 14:53, Maxim Solodovnik a écrit : Everything seems to be ok (it is PHP not json, but code looks ok) What is in db? Om_user table for this user?

Re: REST API : Profile Picture URL

Everything seems to be ok (it is PHP not json, but code looks ok) What is in db? Om_user table for this user? WBR, Maxim (from mobile, sorry for the typos) On Aug 11, 2017 14:46, "Jacob Ouanounou" wrote: > Here it is : (masked some fields with X's) > function

Re: REST API : Profile Picture URL

Here it is : (masked some fields with X's) function connectToRoom($roomId,$options) { $OMConfig=array( "protocol" => "http", "host" => "X", "port" => "5080", "context" => "cursus", "user" =>XXX,

Re: REST API : Profile Picture URL

I need JSON you are sending to be able to help you On Fri, Aug 11, 2017 at 2:18 PM, Jacob Ouanounou wrote: > Hi Maxim, > > I am still trying to solve this issue : I don't succeed to get the > profilePictureUrl set. > > In the doc, I see this field named either profilePictureUrl

Re: REST API : Profile Picture URL

Hi Maxim, I am still trying to solve this issue : I don't succeed to get the profilePictureUrl set. In the doc, I see this field named either profilePictureUrl or profilePictureUri When I set NONE of them I get a picture with a question mark, When I set profiePictureUrl, I get no picture

Re: REST API : Profile Picture URL

This array doesn't make sense :( could var_dump() it? so "real value" for $Photo will be printed On Thu, Jul 27, 2017 at 4:09 PM, Jacob Ouanounou wrote: > Thank you for your answer > > Here is my user array : > > $user=array( > "login" => "cursusA" >

Re: REST API : Profile Picture URL

Thank you for your answer Here is my user array : $user=array( "login" => "cursusA" ,"username" => "Id:".$_SESSION['id'] , "firstname" => $_SESSION['prenom'] , "lastname" => $_SESSION['nom']

Re: REST API : Profile Picture URL

Please do not write personal emails (use Reply All :)) OK let's do investigation together step-by-step you are calling services/user/hash REST function in API it is:

Re: REST API : Profile Picture URL

What description are you expecting to see? UserDTO doesn't have pictureUri, User has this field You can propose PR with better JavaDoc :))) On Thu, Jul 27, 2017 at 3:01 PM, Jacob Ouanounou wrote: > In this page I see something called pictureUri. When I use that keyword, I >

Re: REST API : Profile Picture URL

In this page I see something called pictureUri. When I use that keyword, I get a picture with a question mark, the same as if I don't specify any photo for the user. But if I use the keyword "profilePictureUrl" , I get no picture for the user in the room. (I don't understand the structure of

Re: REST API : Profile Picture URL

You can check properties in API javadocs: http://openmeetings.apache.org/openmeetings-db/apidocs/org/apache/openmeetings/db/dto/user/UserDTO.html?is-external=true it seems pictureUri was dropped during migration could you please file JIRA, should be easy to fix On Thu, Jul 27, 2017 at 2:43 PM,

REST API : Profile Picture URL

Hello, It seems that the user option "profilePictureUrl" that allows to set the picture of the user does not work anymore, or the keyword has changed. I have also tried to set that parameter in room options, without success.

Re: REST API for OM

Surprizing ... Any idea ? Le 26/07/2017 à 13:01, Maxim Solodovnik a écrit : Yes, It is already in a Wiki: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP) <https://github.com/openmeeti

Re: REST API for OM

on to >> OpenMeetings ... BUT instead of entering the room I requested (number 7) I >> get in the home page ! >> >> Surprizing ... >> >> Any idea ? >> >> Le 26/07/2017 à 13:01, Maxim Solodovnik a écrit : >> >> Yes, >> >> It is a

Re: REST API for OM

It is already in a Wiki: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP) <https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-%28in-PHP%29> it shows step-by-step how to: 1) create options: https://gith

Re: REST API for OM

e home page ! > > Surprizing ... > > Any idea ? > > Le 26/07/2017 à 13:01, Maxim Solodovnik a écrit : > > Yes, > > It is already in a Wiki: https://github.com/openmeetings/openmeetings-api- > plugin/wiki/1.-SOAP-REST-API-(in-PHP) > > it shows step-by-step how t

Re: REST API for OM

Any idea ? Le 26/07/2017 à 13:01, Maxim Solodovnik a écrit : Yes, It is already in a Wiki: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP) <https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-%28in-PHP%29> it shows step-by

Re: REST API for OM

m I requested (number 7) I get in the home page ! Surprizing ... Any idea ? Le 26/07/2017 à 13:01, Maxim Solodovnik a écrit : Yes, It is already in a Wiki: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP) <https://github.com/openmeetings/openmeetin

Re: REST API for OM

Yes, It is already in a Wiki: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP) it shows step-by-step how to: 1) create options: https://github.com/openmeetings/openmeetings-api-plugin/wiki/1.-SOAP-REST-API-(in-PHP)#create-config-array 2) perform login https

Re: REST API for OM

jquery, so it cannot be _just used_ To use REST you need client able to send GET/POST/etc. requests. Which one are you using? The error you are getting doesn't make sense :( CSRF checks are not active for REST On Wed, Jul 26, 2017 at 4:30 PM,

Re: REST API for OM

enmeetings/openmeetings-api-plugin/tree/master/src/main/scripts >>>> >>>> On Wed, Jul 26, 2017 at 4:42 PM, Maxim Solodovnik <solomax...@gmail.com> >>>> <solomax...@gmail.com> wrote: >>>> >>>> Could you please

Re: REST API for OM

:42 PM, Maxim Solodovnik <solomax...@gmail.com> >>> <solomax...@gmail.com> wrote: >>> >>> Could you please tell me how are you call the service? >>> >>> Example on http://openmeetings.apache.org/RestAPISample.html requires >>> jquery,

Re: REST API for OM

tell me how are you call the service? >> >> Example on http://openmeetings.apache.org/RestAPISample.html requires >> jquery, so it cannot be _just used_ >> To use REST you need client able to send GET/POST/etc. requests. >> Which one are you using? >> >> The error you

Re: REST API for OM

ed client able to send GET/POST/etc. requests. > Which one are you using? > > The error you are getting doesn't make sense :( CSRF checks are not > active for REST > > On Wed, Jul 26, 2017 at 4:30 PM, Jacob Ouanounou <nav...@free.fr> > <nav...@free.fr>

Re: REST API for OM

t; > On Wed, Jul 26, 2017 at 4:30 PM, Jacob Ouanounou <nav...@free.fr> wrote: >> Back to REST API : I succeed to get the SID, but when I try to get the hash, >> using excatly the code written there : >> http://openmeetings.apache.org/RestAPISample.html , with the s

Re: REST API for OM

:( CSRF checks are not active for REST On Wed, Jul 26, 2017 at 4:30 PM, Jacob Ouanounou <nav...@free.fr> wrote: > Back to REST API : I succeed to get the SID, but when I try to get the hash, > using excatly the code written there : > http://openmeetings.apache.org/RestAPISample.html

Re: REST API for OM

Back to REST API : I succeed to get the SID, but when I try to get the hash, using excatly the code written there : http://openmeetings.apache.org/RestAPISample.html , with the sid I obtained, I get an error (in the console of the browser) : http://35.157.227.184:5080/openmeetings/services

Re: REST API for OM

THANK YOU MAXIM ! It works fine ... Le 26/07/2017 à 09:10, Maxim Solodovnik a écrit : you have to escape your password using JS escape function or urlescape written in any pther language On Wed, Jul 26, 2017 at 1:53 PM, Jacob Ouanounou wrote: Hi Maxim, I have found in the

Re: REST API for OM

you have to escape your password using JS escape function or urlescape written in any pther language On Wed, Jul 26, 2017 at 1:53 PM, Jacob Ouanounou wrote: > Hi Maxim, > > I have found in the log file (in file : 0.0.0.0_access..2017-07-25.log) the > lines corresponding to my

Re: REST API for OM

Hi Maxim, I have found in the log file (in file : 0.0.0.0_access..2017-07-25.log) the lines corresponding to my trials to connect. The request I did (URL) is reproduced without the special characters in the password. It seems logical, since GET mode alters the special characters. The

Re: REST API for OM

You can search it on your server :) it should be located in "log" folder under the folder you have unpacked openmeetings On Tue, Jul 25, 2017 at 7:11 PM, Jacob Ouanounou wrote: > In which directory is this file ? > > Le 25/07/2017 à 13:57, Maxim Solodovnik a écrit : > > is there

Re: REST API for OM

In which directory is this file ? Le 25/07/2017 à 13:57, Maxim Solodovnik a écrit : is there anything suspicious in openmeetings.log file? On Tue, Jul 25, 2017 at 6:54 PM, Jacob Ouanounou > wrote: When I enter this directly on the browser, using

Re: REST API for OM

is there anything suspicious in openmeetings.log file? On Tue, Jul 25, 2017 at 6:54 PM, Jacob Ouanounou wrote: > When I enter this directly on the browser, using the correct user and pwd, > I get this > > {"serviceResult":{"code":-1,"message":"Login failed","type":"ERROR"}} > >

Re: REST API for OM

When I enter this directly on the browser, using the correct user and pwd, I get this {"serviceResult":{"code":-1,"message":"Login failed","type":"ERROR"}} Le 25/07/2017 à 13:47, Maxim Solodovnik a écrit : to login and get SID you can just type in your browser:

Re: REST API for OM

to login and get SID you can just type in your browser: http://35.157.227.184:5080/openmeetings/services/user/login?user=XXX; pass=XXX Here is the link to PHP API (seems to work, just have tested with Moodle) https://github.com/openmeetings/openmeetings-api-plugin Here is the link to Java Unit

Re: REST API for OM

Can you please send me your code, si that I could see a code that works and get inspired ... Le 25/07/2017 à 13:33, Maxim Solodovnik a écrit : just have tested on demo server, works as expected how are you using the service? On Tue, Jul 25, 2017 at 6:28 PM, Jacob Ouanounou

Re: REST API for OM

In a script, java inserted these lines $.ajax({ method: "GET", url: "http://35.157.227.184:5080/openmeetings/services/user/login;, data: {user: 'XXX', pass: 'XXX'}, dataType: "json" }); Le 25/07/2017 à 13:33, Maxim Solodovnik a écrit : just have tested on demo server, works as

Re: REST API for OM

just have tested on demo server, works as expected how are you using the service? On Tue, Jul 25, 2017 at 6:28 PM, Jacob Ouanounou wrote: > I have followed the first example, and I get this error : > (services/user/login) > > No 'Access-Control-Allow-Origin' header is present on

Re: REST API for OM

I have followed the first example, and I get this error : (services/user/login) No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. Le 25/07/2017 à 12:24, Maxim Solodovnik a écrit : Yes, API was changed please check

Re: REST API for OM

Yes, API was changed please check the example I believe it is cleaner now :) On Tue, Jul 25, 2017 at 5:22 PM, Jacob Ouanounou wrote: > In a previous version, I started by using this link to do a session > request : > > http://:5080/openmeetings/services/UserService/getSession >

Re: REST API for OM

In a previous version, I started by using this link to do a session request : http://:5080/openmeetings/services/UserService/getSession to initiate the connection process Now I get this answer :

Re: REST API for OM

It is definitely possible :) Here is sample: http://openmeetings.apache.org/RestAPISample.html Here is the link to the API javadoc: http://openmeetings.apache.org/openmeetings-webservice/apidocs/index.html On Tue, Jul 25, 2017 at 4:57 PM, Jacob Ouanounou wrote: > Hi, > > It

REST API for OM

Hi, It seems that it is not possible anymore to connect to OM server using REST. Is it ? Thank you Le 24/07/2017 à 18:00, Maxim Solodovnik a écrit : Thanks :) Will try to create custom CSS, might take some time :( Will report back here please ping me in case I'll be too silent On Mon, Jul

Re: Open meetings REST API issue

ting response from anyone from Openmeetings. > > Regards, > > Manpreet Bedi > > > > > > From: Bedi, Manpreet (MIND) > Sent: Friday, May 05, 2017 5:14 PM > To: 'user@openmeetings.apache.org' > Subject: FW: Open meetings REST API issue > > > > > > D

RE: Open meetings REST API issue

Hi , I am Still expecting response from anyone from Openmeetings. Regards, Manpreet Bedi From: Bedi, Manpreet (MIND) Sent: Friday, May 05, 2017 5:14 PM To: 'user@openmeetings.apache.org' Subject: FW: Open meetings REST API issue Dear sir, I am facing issue in using the REST API provided

FW: Open meetings REST API issue

Dear sir, I am facing issue in using the REST API provided by open meetings to enter a room. Whenever I enter a room by hitting the below service: $.ajax({ method : "

Open meetings REST API issue

Dear sir, I am facing issue in using the REST API provided by open meetings to enter a room. Whenever I enter a room by hitting the below service: $.ajax({ method : "

Re: REST API

t;>>>FileExplorerItemDTO file, > >>>> InputStream stream) > >>>> throws > >>>> org.apache.openmeetings.webservice.error.ServiceException > >>>> > >>

Re: REST API

>>> to add a folder to the private drive, set parentFileExplorerItemId = 0 >>>> and isOwner to 1/true and externalUserId/externalUserType to a valid user >>>> Parameters:sid - The SID of the User. This SID must be marked as logged >>>> infile - the The file to be addedstrea

Re: REST API

---- >>> >>> How do I pass the FileExplorerItemDTO and, above all, the InputStream >>> through OmGateway.php or OmRestService,php?? >>> >>> Thank you and let me know! >>> >>> Alessio >>> >>> >>> >

Re: REST API

through OmGateway.php or OmRestService,php?? >> >> Thank you and let me know! >> >> Alessio >> >> >> >> >> 2016-09-19 19:13 GMT+02:00 Coscend@OM <om.insig...@coscend.com>: >> >>> Hello Alessio, >>> >>> Guide and snippe

Re: REST API

olutions >> Web site: www.Coscend.com >> ------ >> CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail >> Messages from Coscend Communications Solutions' posted at: >> http://www.Coscend.com/Te

Re: REST API

mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > > > > -Original Message- > From: Alessio Falsetti [mailto:alessio.false...@eng.it] > Sent: Monday, September 19, 2016 12:08 PM > To: user@open

RE: REST API

] Sent: Monday, September 19, 2016 12:08 PM To: user@openmeetings.apache.org Subject: REST API Hi, through the REST API of OpenMeetings (3.1.1), I'm trying to upload files into a room. I'm trying to use the FileWebService API to add the files. Reading the documentation I seem to have understood

REST API

Hi, through the REST API of OpenMeetings (3.1.1), I'm trying to upload files into a room. I'm trying to use the FileWebService API to add the files. Reading the documentation I seem to have understood that the function to be used is ADD, but until now I have not been successful use

Re: Cannot reproduce REST API example

n:* Maxim Solodovnik [mailto:solomax...@gmail.com] > *Gesendet:* Friday, September 2, 2016 4:58 AM > *An:* Openmeetings user-list <user@openmeetings.apache.org> > *Betreff:* Re: Cannot reproduce REST API example > > > > Sure, > > > > but this would be not for f

AW: Cannot reproduce REST API example

o:solomax...@gmail.com] Gesendet: Friday, September 2, 2016 4:58 AM An: Openmeetings user-list <user@openmeetings.apache.org> Betreff: Re: Cannot reproduce REST API example Sure, but this would be not for free ... :))) Please try 3.1.3-SNAPSHOT and edit API Wiki :)) so to get links to Rec

Re: Cannot reproduce REST API example

get the other URL? J > > > > Cheers > > Andre > > > > *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com] > *Gesendet:* Thursday, September 1, 2016 7:09 PM > > *An:* Openmeetings user-list <user@openmeetings.apache.org> > *Betreff:* Re: Cannot reproduce RES

AW: Cannot reproduce REST API example

: Thursday, September 1, 2016 7:09 PM An: Openmeetings user-list <user@openmeetings.apache.org> Betreff: Re: Cannot reproduce REST API example BTW recording by id is only available to logged in OM user To view recording by external user you need other URL WBR, Maxim (from mobile, sorry for the

Re: Cannot reproduce REST API example

s >> Andre >> >> >> >> *Von:* Maxim Solodovnik [mailto:solomax...@gmail.com] >> *Gesendet:* Thursday, September 1, 2016 6:17 PM >> *An:* Openmeetings user-list <user@openmeetings.apache.org> >> *Betreff:* Re: Cannot reproduce REST API examp

  1   2   >