[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417264#comment-17417264
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 600abcb1432a3bdd5900c90fbe75187f5e5c2b09 in openmeetings's branch
refs/heads/master from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=600abcb ]
OPENMEETINGS-2667 Update Info Service with correct response schema and an
example response.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417262#comment-17417262
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 4e3d59234231a4485210a89d564b22005ad5e00a in openmeetings's branch
refs/heads/master from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=4e3d592 ]
OPENMEETINGS-2667 Fix RoomService to have correct response schema and an
example value.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417263#comment-17417263
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 642f4c2aef147861ed469a8ddadba03f2cba8dfd in openmeetings's branch
refs/heads/master from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=642f4c2 ]
OPENMEETINGS-2667 Fix Recording and WbService to have schema matching response
and example values.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417261#comment-17417261
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 18766503ef073e80f29cb051c8683148b276f44e in openmeetings's branch
refs/heads/master from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=1876650 ]
OPENMEETINGS-2667 Fix schema with root element and example values for responses.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417259#comment-17417259
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 845995e2d5bca4189fff565b494a56b52d8232a0 in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=845995e ]
OPENMEETINGS-2667 Update CalendarService with response schema matching actual
response and add an example value.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417257#comment-17417257
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit b949e0c9f19d606c2e8aaf911df7a97f1115dc18 in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b949e0c ]
OPENMEETINGS-2667 Update FileService to have correct schema definition and an
example response.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417255#comment-17417255
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 77f5211cdb80995fdd3ed930bb9f860527d81659 in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=77f5211 ]
OPENMEETINGS-2667 Fix GroupService to have correct response schema definition
and an example value.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417253#comment-17417253
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 600abcb1432a3bdd5900c90fbe75187f5e5c2b09 in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=600abcb ]
OPENMEETINGS-2667 Update Info Service with correct response schema and an
example response.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417251#comment-17417251
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 642f4c2aef147861ed469a8ddadba03f2cba8dfd in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=642f4c2 ]
OPENMEETINGS-2667 Fix Recording and WbService to have schema matching response
and example values.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> json response and have that wrapper as meta information for the
> swagger.annotation to the swagger annotation.
> It would be better to drop the root / wrapping element on the long run in
> CXF. But that would be a breaking change to the API and probably require a
> new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses at the moment.
> Also it might be better to generate those into separated classes so that the
> API class won't get too large to read.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417248#comment-17417248
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 4e3d59234231a4485210a89d564b22005ad5e00a in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=4e3d592 ]
OPENMEETINGS-2667 Fix RoomService to have correct response schema and an
example value.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> and only supply that to the swagger annotation.
> Its not super nice. But it works for now. It would be better to drop the root
> / wrapping element on the long run. But that would be a breaking change to
> the API and probably require a new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses. Also it might be
> better to generate those into separated classes so that the API class won't
> get too large to read through
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema and provide example responses
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417243#comment-17417243
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 18766503ef073e80f29cb051c8683148b276f44e in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=1876650 ]
OPENMEETINGS-2667 Fix schema with root element and example values for responses.
> Generated swagger has incorrect response, missing root element in schema and
> provide example responses
> --
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> This ticket addresses 2 items
> h1. Wrapping response generated schema into Root element
> The way how CXF generates the JSON a response looks like this:
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> and only supply that to the swagger annotation.
> Its not super nice. But it works for now. It would be better to drop the root
> / wrapping element on the long run. But that would be a breaking change to
> the API and probably require a new version.
> h1. Providing Example responses
> There isn't a possibility to provide example responses. Also it might be
> better to generate those into separated classes so that the API class won't
> get too large to read through
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2667) Generated swagger has incorrect response, missing root element in schema
[
https://issues.apache.org/jira/browse/OPENMEETINGS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417241#comment-17417241
]
ASF subversion and git services commented on OPENMEETINGS-2667:
---
Commit 4ed7cf0318a657b217382d311b26f842c4d7b4e6 in openmeetings's branch
refs/heads/feature/OPENMEETINGS-2667-update-schema-definition-for-response-wrapping-in-root-element
from Sebastian Wagner
[ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=4ed7cf0 ]
OPENMEETINGS-2667 Add ServiceResult updated schema wrapper to match CXF-RS
response structure including root element.
> Generated swagger has incorrect response, missing root element in schema
>
>
> Key: OPENMEETINGS-2667
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2667
> Project: Openmeetings
> Issue Type: Improvement
> Components: Documentation, SOAP/REST API
>Affects Versions: 7.0.0
>Reporter: Sebastian Wagner
>Assignee: Sebastian Wagner
>Priority: Major
> Fix For: 7.0.0
>
>
> The way how CXF generates the JSON a response looks like this:
>
> {code:java}
> {
> "serviceResult": {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> }
> {code}
> It wraps it into a "serviceResult", while that part is not really part of the
> schema.
> Based on our API definition it would expect:
> {code:java}
> {
> "message": "9f51e7d6-e662-463a-b410-7bf31357f111",
> "type": "SUCCESS"
> }
> {code}
> => no wrapping into a "serviceResult": \{ ... }
> There is a way to turn off this generation of wrapping / root elements in
> CXF. But that would break existing clients.
> So the challenge is to generate an API definition that actually matches the
> response.
> The only way to generate the correct documentation seems to be to wrap the
> schema class into a wrapper object so that the schema matches the generated
> and only supply that to the swagger annotation.
> Its not super nice. But it works for now. It would be better to drop the root
> / wrapping element on the long run. But that would be a breaking change to
> the API and probably require a new version.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2666) Backup import should be improved
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415576#comment-17415576 ] ASF subversion and git services commented on OPENMEETINGS-2666: --- Commit b5bfab61c613963a7ca455d819df28fa8e997264 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b5bfab6 ] [OPENMEETINGS-2666] Backup import is improved > Backup import should be improved > > > Key: OPENMEETINGS-2666 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2666 > Project: Openmeetings > Issue Type: Improvement > Components: Import/Export >Affects Versions: 6.1.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > # Archive should be unzipped to unpredictable folder > # Files should be deleted even if there was an exception during import -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2637) Move to bootstrap 5
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415346#comment-17415346 ] ASF subversion and git services commented on OPENMEETINGS-2637: --- Commit 65a56e76536e8dac3df655b164b9df4351cd7818 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=65a56e7 ] [OPENMEETINGS-2637] minor UI issues > Move to bootstrap 5 > --- > > Key: OPENMEETINGS-2637 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2637 > Project: Openmeetings > Issue Type: Task > Components: UI >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Move to bootstrap 5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2665) "Start sharing" icon TV not show it in some circunstanves
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415274#comment-17415274 ] ASF subversion and git services commented on OPENMEETINGS-2665: --- Commit b2f565b175fc2b091714ec4d3f6a660a7ce9605a in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b2f565b ] [OPENMEETINGS-2640, OPENMEETINGS-2665] wicket-bootstrap > "Start sharing" icon TV not show it in some circunstanves > - > > Key: OPENMEETINGS-2665 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2665 > Project: Openmeetings > Issue Type: Test > Components: Screen-sharing >Affects Versions: 7.0.0 > Environment: ## OpenMeetings 7.0.0 #35 > # Server: Ubuntu 18.04 - OM 7.0.0 #35 > # Clients: Ubuntu 18.04 - Firefox 91 *** OSx 11.5.2 - Firefox 92 - Chrome 93 >Reporter: Alvaro >Assignee: Maxim Solodovnik >Priority: Minor > Fix For: 7.0.0 > > Attachments: openmeetings-1.log, openmeetings-2.log > > > The administrator user enters the room, where there is no one, and clicks on > the > TV icon called “Start sharing”. So it correctly shows the little > window with the options “Start sharing” or “Start recording”. > But if: > The admin user enters the room and waits until a non-admin user > enter also, then press, the administrator, on the TV icon called "Start > sharing“ and nothing happens. > Need push refresh administrator button and after will work right if press on > TV icon, > then will show the little window with the share or recording options. > If the normal user clicks on the monitor icon called "Start sharing", be alone > or with the administrator in the room, it will always work correctly. > Apparently this anomaly only affects the administrator in the mentioned > circumstances. > Attached logs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415273#comment-17415273 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit b2f565b175fc2b091714ec4d3f6a660a7ce9605a in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b2f565b ] [OPENMEETINGS-2640, OPENMEETINGS-2665] wicket-bootstrap > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415080#comment-17415080 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit c46bdc7bfa8836f72087bba495fa69e815c46c53 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=c46bdc7 ] [OPENMEETINGS-2640] wicketstuff, junit, tomcat > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414589#comment-17414589 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 9756d54355b480a8646a69a8d22a7b21326bea1b in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=9756d54 ] OPENMEETINGS-2420 Add both release and other news section for Node.js and OpenAPI swagger doc link. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414014#comment-17414014 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit de05f65d7e73690db0fe228f875d94aa3ec29c09 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=de05f65 ] [OPENMEETINGS-2640] wicket, maven-war-plugin > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17414012#comment-17414012 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit f897cafa38c726c84934b01d8750da96412f1d59 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=f897caf ] [OPENMEETINGS-2640] wicket namespace is updated > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413911#comment-17413911 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 882e265dcc8fdb1935e54e8013ace41cb5d24da6 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=882e265 ] OPENMEETINGS-2420 Update news section on OpenAPI spec and Node.js integration. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2664) Fix CONSUMES tag so that generated swagger understands FormParams as multipart-form
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413694#comment-17413694 ] ASF subversion and git services commented on OPENMEETINGS-2664: --- Commit feb25454c7b60f725308f3c2dd5d97299c297c7f in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=feb2545 ] Revert "OPENMEETINGS-2664 Fix consumes tag so generated swagger is correct." This reverts commit e01c014430f0691587a7f5ddf35f9c774aac415b. > Fix CONSUMES tag so that generated swagger understands FormParams as > multipart-form > --- > > Key: OPENMEETINGS-2664 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2664 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > The generated swagger is wrong as it thinks @ FormParam is a json body, while > it is expected as multipart/form-data parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413629#comment-17413629 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 828f1f02af25b0406142a69ee80a32409c8d038c in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=828f1f0 ] OPENMEETINGS-2661 Fix another typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413628#comment-17413628 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 828f1f02af25b0406142a69ee80a32409c8d038c in openmeetings's branch refs/heads/feature/OPENMEETINGS-2661-fix-another-typo from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=828f1f0 ] OPENMEETINGS-2661 Fix another typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413630#comment-17413630 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit a57aa103c6f3c325037e1e02f37fd05197a5c6e4 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=a57aa10 ] Merge pull request #155 from apache/feature/OPENMEETINGS-2661-fix-another-typo OPENMEETINGS-2661 Fix another typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413627#comment-17413627 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit d62a3b33f8252cea139d6b64427f2c733b0553b4 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2661-fix-typo-and-link from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=d62a3b3 ] OPENMEETINGS-2661 Fix another typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413625#comment-17413625 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 97d173040fa11791faf10b4d129dd075cd77729a in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=97d1730 ] OPENMEETINGS-2661 Fix link and typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413626#comment-17413626 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 29b6c33ad964db5947120a31749bc7bcc941dc37 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=29b6c33 ] Merge pull request #153 from apache/feature/OPENMEETINGS-2661-fix-typo-and-link OPENMEETINGS-2661 Fix link and typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413624#comment-17413624 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 97d173040fa11791faf10b4d129dd075cd77729a in openmeetings's branch refs/heads/feature/OPENMEETINGS-2661-fix-typo-and-link from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=97d1730 ] OPENMEETINGS-2661 Fix link and typo. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413622#comment-17413622 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 73a96cdf1757579d46dca4043b698504191a187d in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=73a96cd ] OPENMEETINGS-2661 Add Rest examples and add Node.js Module. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413623#comment-17413623 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 1fc5032731aff29af973e7a978e0ca834290ce56 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=1fc5032 ] Merge pull request #152 from apache/feature/OPENMEETINGS-2661-update-rest-examples-add-node-js-module OPENMEETINGS-2661 Add Rest examples and add Node.js Module. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2661) Updated Rest API Example
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413621#comment-17413621 ] ASF subversion and git services commented on OPENMEETINGS-2661: --- Commit 73a96cdf1757579d46dca4043b698504191a187d in openmeetings's branch refs/heads/feature/OPENMEETINGS-2661-update-rest-examples-add-node-js-module from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=73a96cd ] OPENMEETINGS-2661 Add Rest examples and add Node.js Module. > Updated Rest API Example > > > Key: OPENMEETINGS-2661 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2661 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2664) Fix CONSUMES tag so that generated swagger understands FormParams as multipart-form
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413459#comment-17413459 ] ASF subversion and git services commented on OPENMEETINGS-2664: --- Commit 65cceb32574227146a668daa1b94b3a99ee148fb in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=65cceb3 ] Merge pull request #151 from apache/feature/OPENMEETINGS-2664-fix-consumes-tag-for-rest-apis OPENMEETINGS-2664 Fix consumes tag so generated swagger is correct. > Fix CONSUMES tag so that generated swagger understands FormParams as > multipart-form > --- > > Key: OPENMEETINGS-2664 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2664 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > The generated swagger is wrong as it thinks @ FormParam is a json body, while > it is expected as multipart/form-data parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2664) Fix CONSUMES tag so that generated swagger understands FormParams as multipart-form
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413458#comment-17413458 ] ASF subversion and git services commented on OPENMEETINGS-2664: --- Commit e01c014430f0691587a7f5ddf35f9c774aac415b in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=e01c014 ] OPENMEETINGS-2664 Fix consumes tag so generated swagger is correct. > Fix CONSUMES tag so that generated swagger understands FormParams as > multipart-form > --- > > Key: OPENMEETINGS-2664 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2664 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > The generated swagger is wrong as it thinks @ FormParam is a json body, while > it is expected as multipart/form-data parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2664) Fix CONSUMES tag so that generated swagger understands FormParams as multipart-form
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413457#comment-17413457 ] ASF subversion and git services commented on OPENMEETINGS-2664: --- Commit e01c014430f0691587a7f5ddf35f9c774aac415b in openmeetings's branch refs/heads/feature/OPENMEETINGS-2664-fix-consumes-tag-for-rest-apis from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=e01c014 ] OPENMEETINGS-2664 Fix consumes tag so generated swagger is correct. > Fix CONSUMES tag so that generated swagger understands FormParams as > multipart-form > --- > > Key: OPENMEETINGS-2664 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2664 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > The generated swagger is wrong as it thinks @ FormParam is a json body, while > it is expected as multipart/form-data parameters -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411782#comment-17411782 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit e1de3d2229bb0da304c6a3e809639ac914342a39 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=e1de3d2 ] [OPENMEETINGS-2640] maven-javadoc-plugin, font-awesome > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2659) Can´t clean whiteboard
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411358#comment-17411358 ] ASF subversion and git services commented on OPENMEETINGS-2659: --- Commit 4a656bd5773514a075ac6efc68c3eb911ed193dc in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=4a656bd ] [OPENMEETINGS-2659] vertical lines in calendar > Can´t clean whiteboard > --- > > Key: OPENMEETINGS-2659 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2659 > Project: Openmeetings > Issue Type: Test > Components: WhiteBoard >Affects Versions: 7.0.0 > Environment: Server: Ubuntu 18.04 - OM 7.0.0 #24 > Client: OSx 11.5.2 - FF 91 - Safari 14.1.2 - Chrome > Client: Ubuntu 18.04 - Firefox 91 >Reporter: Alvaro >Assignee: Maxim Solodovnik >Priority: Major > Attachments: openmeetings.log > > > # Calendar page not show vertical lines. > ## In Conference room an user, administrator or not, > drag a file to whiteboard and after want clean it and > can do it. But if after clean it drag a new file to > whiteboard and try to clean it pushing: > Clean whiteboard ==> Do you really want delete… ==> OK, > nothing happens. > Press Cancel button and the first time works right, > but the second and succesives times will not work. > Attached log. > -- -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410057#comment-17410057 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 66b8d3095bc9758a6faf8a77bba01be393ae9f24 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=66b8d30 ] Merge pull request #150 from apache/feature/OPENMEETINGS-2660-fix-api-docs-generated-API-order OPENMEETINGS-2660 Update specs generated so that ordering in generated docs is defined. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410056#comment-17410056 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 7ea970615ac128bc06afd4d55d034ca8f697dafe in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=7ea9706 ] OPENMEETINGS-2660 Update specs generated so that ordering in generated docs is defined. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410055#comment-17410055 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 7ea970615ac128bc06afd4d55d034ca8f697dafe in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-fix-api-docs-generated-API-order from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=7ea9706 ] OPENMEETINGS-2660 Update specs generated so that ordering in generated docs is defined. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409815#comment-17409815 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 397efd2de8c48c77c7822754385c9979ce7dc4ae in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=397efd2 ] OPENMEETINGS-2660 Add Rest API documentation annotation for FileService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409817#comment-17409817 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit cd2985015db3083cfc6e6ef5c2052870833437fe in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=cd29850 ] OPENMEETINGS-2660 Add Rest API documentation annotation for CalendarService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409814#comment-17409814 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 26ee1b552b38e4bbd80a2a9abe629582f0e5ca63 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=26ee1b5 ] OPENMEETINGS-2660 Add Rest API documentation annotation for GroupService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409811#comment-17409811 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 6b078d55585cb68289c44ce8c3159ac8415f020e in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6b078d5 ] OPENMEETINGS-2660 Add RecordingWebService.java API Rest docs. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409810#comment-17409810 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 8b6eb93e07793dcbe7b67ec099af66e66cdb25e7 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8b6eb93 ] OPENMEETINGS-2660 Update and add WbWebService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409816#comment-17409816 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 26d49e8cb8bc42ba7b4d44d47aecc5d7d714cc8b in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=26d49e8 ] OPENMEETINGS-2660 Add Rest API documentation annotation for ErrorService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409818#comment-17409818 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 082ceca293a31dd3299954cb928ad2905ac18af4 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=082ceca ] Merge pull request #149 from apache/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services OPENMEETINGS-2660 Update response codes objects and remaining Services > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409813#comment-17409813 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit b5d15442b676101f1de3252ccd654e9476e062b9 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b5d1544 ] OPENMEETINGS-2660 Add InfoService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409812#comment-17409812 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit c7f34292975f101c4c201e75f873af1dbc3ea915 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=c7f3429 ] OPENMEETINGS-2660 Add NetTestWebService and RecordingWebService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409809#comment-17409809 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 55fcb949ae2dd1d482b89835c662a60f946244b8 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=55fcb94 ] OPENMEETINGS-2660 Update response codes and objects to be generated. Add UserService API tags for documentation. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409808#comment-17409808 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit cd2985015db3083cfc6e6ef5c2052870833437fe in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=cd29850 ] OPENMEETINGS-2660 Add Rest API documentation annotation for CalendarService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409805#comment-17409805 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 26d49e8cb8bc42ba7b4d44d47aecc5d7d714cc8b in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=26d49e8 ] OPENMEETINGS-2660 Add Rest API documentation annotation for ErrorService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409802#comment-17409802 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 397efd2de8c48c77c7822754385c9979ce7dc4ae in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=397efd2 ] OPENMEETINGS-2660 Add Rest API documentation annotation for FileService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409790#comment-17409790 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit b5d15442b676101f1de3252ccd654e9476e062b9 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b5d1544 ] OPENMEETINGS-2660 Add InfoService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409791#comment-17409791 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 26ee1b552b38e4bbd80a2a9abe629582f0e5ca63 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=26ee1b5 ] OPENMEETINGS-2660 Add Rest API documentation annotation for GroupService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409787#comment-17409787 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 6b078d55585cb68289c44ce8c3159ac8415f020e in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6b078d5 ] OPENMEETINGS-2660 Add RecordingWebService.java API Rest docs. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409788#comment-17409788 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit c7f34292975f101c4c201e75f873af1dbc3ea915 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=c7f3429 ] OPENMEETINGS-2660 Add NetTestWebService and RecordingWebService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409781#comment-17409781 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 8b6eb93e07793dcbe7b67ec099af66e66cdb25e7 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8b6eb93 ] OPENMEETINGS-2660 Update and add WbWebService. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2660) Updated Swagger Rest API Docs
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409770#comment-17409770 ] ASF subversion and git services commented on OPENMEETINGS-2660: --- Commit 55fcb949ae2dd1d482b89835c662a60f946244b8 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2660-update-swagger-rest-api-docs-additional-Web-Services from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=55fcb94 ] OPENMEETINGS-2660 Update response codes and objects to be generated. Add UserService API tags for documentation. > Updated Swagger Rest API Docs > -- > > Key: OPENMEETINGS-2660 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2660 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation, SOAP/REST API >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Labels: API, Doc > Fix For: 7.0.0 > > > Separated Jira to track fixing up the remaining Service Definitions in the > API Docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409720#comment-17409720 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit dcb1235895a71985f8f541a790011d096231d45e in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=dcb1235 ] Merge branch 'master' into feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409721#comment-17409721 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit ad654ee505174a5dccee27a8f37b9e541c57b4f0 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ad654ee ] OPENMEETINGS-2420 Fix typo in generated json. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409719#comment-17409719 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 7db3f9a2584f947b86ef95c9eb9852f3ce3932af in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=7db3f9a ] OPENMEETINGS-2420 Update Rest API docs for RoomService. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409722#comment-17409722 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 525bd84b59d130180fa758cb841da3c7c53f2c96 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=525bd84 ] Merge pull request #148 from apache/feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService Feature/openmeetings 2420 update swagger rest api docs room service > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409277#comment-17409277 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit ad654ee505174a5dccee27a8f37b9e541c57b4f0 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ad654ee ] OPENMEETINGS-2420 Fix typo in generated json. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409275#comment-17409275 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 7db3f9a2584f947b86ef95c9eb9852f3ce3932af in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=7db3f9a ] OPENMEETINGS-2420 Update Rest API docs for RoomService. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409276#comment-17409276 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit dcb1235895a71985f8f541a790011d096231d45e in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=dcb1235 ] Merge branch 'master' into feature/OPENMEETINGS-2420-update-swagger-rest-api-docs-RoomService > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2652) Can´t send invitation from rooms or Calendar
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408733#comment-17408733 ] ASF subversion and git services commented on OPENMEETINGS-2652: --- Commit 2f802e9d7d1b0df69e79dacb2eb18958585b7465 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=2f802e9 ] [OPENMEETINGS-2652] test is fixed > Can´t send invitation from rooms or Calendar > > > Key: OPENMEETINGS-2652 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2652 > Project: Openmeetings > Issue Type: Bug > Components: Calendar, Room >Affects Versions: 7.0.0 > Environment: Server: Ubuntu 18.04 - OM 700 #15 > Client: OSx 11.5.2 - Firefox 91 - Safari 14.1.2 > Client: Ubuntu 18.04 - Firefox 91 >Reporter: Alvaro >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > Attachments: Calendar no show Attendees-1.png, Calendar without > vertical lines.png, Rooms no show Recipient-1.png, openmeetings.log > > > # When try send an invitation from rooms and clic > on Recipient box, not show any user (nothing happens). > # When try send a meeting from Calendar and clic > on Attendees box, not show any user (nothing happens). > # Calendar page don´t show vertical lines. > Attached captures and log. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408732#comment-17408732 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 0d082594b3e36437177306b6aff8d426697419e2 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=0d08259 ] [OPENMEETINGS-2420] whitespaces, dependency versions > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408652#comment-17408652 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 17c1fa027ec8196c8a7dcf3af629cbe5e0674ec8 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=17c1fa0 ] OPENMEETINGS-2420 Update dependency to move to top level. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408653#comment-17408653 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 6e202afe964a3f8095789e66b1941b3e27e216ff in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6e202af ] Merge pull request #147 from apache/feature/OPENMEETINGS-2420-generate-swagger-improvements OPENMEETINGS-2420 Update documentation and tagging for documenting Rest API. Sync with website > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408651#comment-17408651 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 9fcc79f356293b79d6437161666de55b27663716 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=9fcc79f ] OPENMEETINGS-2420 Update documentation and tagging for documenting Rest API. Sync with website. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408647#comment-17408647 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 17c1fa027ec8196c8a7dcf3af629cbe5e0674ec8 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-generate-swagger-improvements from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=17c1fa0 ] OPENMEETINGS-2420 Update dependency to move to top level. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408533#comment-17408533 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 9fcc79f356293b79d6437161666de55b27663716 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-generate-swagger-improvements from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=9fcc79f ] OPENMEETINGS-2420 Update documentation and tagging for documenting Rest API. Sync with website. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408381#comment-17408381 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit a8e002786d336350b15a6ef16b926542323e76ed in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=a8e0027 ] Merge pull request #146 from apache/feature/OPENMEETINGS-2420-generate-swagger-and-provide-to-users-using-swagger-ui OPENMEETINGS-2420 Generates swagger and update generated website to link swagger doc > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408380#comment-17408380 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 6c233f3b52b9e1ff417402044d5203363fafae46 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6c233f3 ] OPENMEETINGS-2420 Add additional tab part2. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408378#comment-17408378 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 595e2afe6611bc2bc855a0542fb0137a15b8d2f5 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=595e2af ] OPENMEETINGS-2420 GEnerates swagger and update generated website to link swagger doc. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408379#comment-17408379 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit ed711d93fea0038bc0ebc36240307de8fc0e945e in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ed711d9 ] OPENMEETINGS-2420 Add additional tab. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408377#comment-17408377 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 6c233f3b52b9e1ff417402044d5203363fafae46 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-generate-swagger-and-provide-to-users-using-swagger-ui from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6c233f3 ] OPENMEETINGS-2420 Add additional tab part2. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408376#comment-17408376 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit ed711d93fea0038bc0ebc36240307de8fc0e945e in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-generate-swagger-and-provide-to-users-using-swagger-ui from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ed711d9 ] OPENMEETINGS-2420 Add additional tab. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2420) Discuss and publish API Docs as swagger - Generate swagger from code
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408039#comment-17408039 ] ASF subversion and git services commented on OPENMEETINGS-2420: --- Commit 595e2afe6611bc2bc855a0542fb0137a15b8d2f5 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2420-generate-swagger-and-provide-to-users-using-swagger-ui from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=595e2af ] OPENMEETINGS-2420 GEnerates swagger and update generated website to link swagger doc. > Discuss and publish API Docs as swagger - Generate swagger from code > > > Key: OPENMEETINGS-2420 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2420 > Project: Openmeetings > Issue Type: Bug > Components: SOAP/REST API >Affects Versions: 5.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Major > Fix For: 7.0.0 > > > I would like to explore how to publish the API docs as swagger document. > The JavaDocs are nice, but I think most of us are using swagger these days. > And you can actually generate swagger docs automatically published from the > code based on the annotations. > I would like to discuss and try that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2652) Can´t send invitation from rooms or Calendar
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407772#comment-17407772 ] ASF subversion and git services commented on OPENMEETINGS-2652: --- Commit c166be61fefdae66f7111de59dd0f4403164b9a8 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=c166be6 ] [OPENMEETINGS-2652] multi-select should work better > Can´t send invitation from rooms or Calendar > > > Key: OPENMEETINGS-2652 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2652 > Project: Openmeetings > Issue Type: Bug > Components: Calendar, Room >Affects Versions: 7.0.0 > Environment: Server: Ubuntu 18.04 - OM 700 #15 > Client: OSx 11.5.2 - Firefox 91 - Safari 14.1.2 > Client: Ubuntu 18.04 - Firefox 91 >Reporter: Alvaro >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > Attachments: Calendar no show Attendees-1.png, Calendar without > vertical lines.png, Rooms no show Recipient-1.png, openmeetings.log > > > # When try send an invitation from rooms and clic > on Recipient box, not show any user (nothing happens). > # When try send a meeting from Calendar and clic > on Attendees box, not show any user (nothing happens). > # Calendar page don´t show vertical lines. > Attached captures and log. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406628#comment-17406628 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 600d4116245f8e7b0da3d359b169988d58f009c1 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=600d411 ] [OPENMEETINGS-2640] wicket-bootstrap, prometheus > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2655) Minor ui fix for icons, see attached screenshots
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406518#comment-17406518 ] ASF subversion and git services commented on OPENMEETINGS-2655: --- Commit 88a6de9e9c76e12996978864b948cb1f02b9c370 in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=88a6de9 ] OPENMEETINGS-2655 Adjust sidebar and desktop sharer icon to fit into button and menu. (#145) > Minor ui fix for icons, see attached screenshots > > > Key: OPENMEETINGS-2655 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2655 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2021-08-29-16-39-09-525.png, > image-2021-08-29-16-40-39-274.png, image-2021-08-29-16-45-02-723.png, > image-2021-08-29-16-45-14-775.png > > > Fix the following minor UI things: > Close icon for sidebar too large: > !image-2021-08-29-16-39-09-525.png! > Desktop sharer icon too large: > !image-2021-08-29-16-40-39-274.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2654) Update build instructions with new commands for compiling NPM
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406517#comment-17406517 ] ASF subversion and git services commented on OPENMEETINGS-2654: --- Commit 50f8b34c6b875d584ff8192bdee71408295bf7ed in openmeetings's branch refs/heads/master from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=50f8b34 ] OPENMEETINGS-2654 Update website with new commands for updating JS code dynamically. (#144) > Update build instructions with new commands for compiling NPM > - > > Key: OPENMEETINGS-2654 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2654 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > Update website with new commands for compiling JS and CSS without running the > entire build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2655) Minor ui fix for icons, see attached screenshots
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406361#comment-17406361 ] ASF subversion and git services commented on OPENMEETINGS-2655: --- Commit f6cfd030d2d6cad5fa4e656026cb344371e58566 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2655-adjust-icons-to-fit-buttonAndMenu from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=f6cfd03 ] OPENMEETINGS-2655 Adjust sidebar and desktop sharer icon to fit into button and menu. > Minor ui fix for icons, see attached screenshots > > > Key: OPENMEETINGS-2655 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2655 > Project: Openmeetings > Issue Type: Improvement > Components: UI >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > Attachments: image-2021-08-29-16-39-09-525.png, > image-2021-08-29-16-40-39-274.png, image-2021-08-29-16-45-02-723.png, > image-2021-08-29-16-45-14-775.png > > > Fix the following minor UI things: > Close icon for sidebar too large: > !image-2021-08-29-16-39-09-525.png! > Desktop sharer icon too large: > !image-2021-08-29-16-40-39-274.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2654) Update build instructions with new commands for compiling NPM
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406357#comment-17406357 ] ASF subversion and git services commented on OPENMEETINGS-2654: --- Commit 86acb6ed49af745eeac0dbdbd9b396e35f7fc059 in openmeetings's branch refs/heads/feature/OPENMEETINGS-2654-update-js-build-instructions from Sebastian Wagner [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=86acb6e ] OPENMEETINGS-2654 Update website with new commands for updating JS code dynamically. > Update build instructions with new commands for compiling NPM > - > > Key: OPENMEETINGS-2654 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2654 > Project: Openmeetings > Issue Type: Improvement > Components: Documentation >Affects Versions: 7.0.0 >Reporter: Sebastian Wagner >Assignee: Sebastian Wagner >Priority: Minor > Fix For: 7.0.0 > > > Update website with new commands for compiling JS and CSS without running the > entire build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2637) Move to bootstrap 5
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405322#comment-17405322 ] ASF subversion and git services commented on OPENMEETINGS-2637: --- Commit fee30bd7446cdd34dbe2e1c1c42c77bd0b81c175 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=fee30bd ] [OPENMEETINGS-2637] Merge branch 'bootstrap-5' > Move to bootstrap 5 > --- > > Key: OPENMEETINGS-2637 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2637 > Project: Openmeetings > Issue Type: Task > Components: UI >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Move to bootstrap 5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2637) Move to bootstrap 5
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405321#comment-17405321 ] ASF subversion and git services commented on OPENMEETINGS-2637: --- Commit 45be7abc59cc7da8947329bcde473bf055b5ae0b in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=45be7ab ] [OPENMEETINGS-2637] More work on migration > Move to bootstrap 5 > --- > > Key: OPENMEETINGS-2637 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2637 > Project: Openmeetings > Issue Type: Task > Components: UI >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Move to bootstrap 5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2637) Move to bootstrap 5
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405320#comment-17405320 ] ASF subversion and git services commented on OPENMEETINGS-2637: --- Commit b13bf8245625d74b1bb95371e667f2adf66b16d6 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=b13bf82 ] [OPENMEETINGS-2637] initial commit > Move to bootstrap 5 > --- > > Key: OPENMEETINGS-2637 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2637 > Project: Openmeetings > Issue Type: Task > Components: UI >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Move to bootstrap 5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404921#comment-17404921 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 8494d0cd5895d2cb639aa414e301ba283cfdba3e in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8494d0c ] [OPENMEETINGS-2640] ojdbc, tika, mockito > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404919#comment-17404919 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 613c13cc807e86ab4d8e5c958ea06d9b2b471959 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=613c13c ] [OPENMEETINGS-2640] commons-pool, mssql > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404922#comment-17404922 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit ebddc8e8a1ab036276dd5330daf12c66cc710ab5 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ebddc8e ] [OPENMEETINGS-2640] tika > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404920#comment-17404920 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 41737f4459089330971e6da3cb792c80c2bbb366 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=41737f4 ] [OPENMEETINGS-2640] xstream > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2639) Add internal password user when send inivitation from room
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396783#comment-17396783 ] ASF subversion and git services commented on OPENMEETINGS-2639: --- Commit e5f6815235573ab820f9f5352083a5dfe83002cc in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=e5f6815 ] [OPENMEETINGS-2639] invitation hash should be generated for password protected invitations > Add internal password user when send inivitation from room > -- > > Key: OPENMEETINGS-2639 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2639 > Project: Openmeetings > Issue Type: Improvement > Components: Email >Affects Versions: 6.1.0 > Environment: Ubuntu 18.04 - OM 6.1.0 #323 >Reporter: Alvaro >Assignee: Maxim Solodovnik >Priority: Minor > > Add active internal password user when send inivitation from room -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396383#comment-17396383 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 3a1b9c74115851bd7f3bba03f0f0df7af37d0765 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=3a1b9c7 ] [OPENMEETINGS-2640] tomcat > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393206#comment-17393206 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 51c20bf014400dc158e0c1a1f4d940b1bd8c57fa in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=51c20bf ] [OPENMEETINGS-2640] commons-dbcp, maven-source-plugin > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388149#comment-17388149 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 8ac48dbaa1d0d330a0287cb62428643e5ba30be1 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=8ac48db ] [OPENMEETINGS-2640] some exclusions are added > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387245#comment-17387245 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 88c38eebcea6ff245e96682c53f7ee9661f6d55d in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=88c38ee ] [OPENMEETINGS-2640] logback > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2640) (7.0.0) Libraries should be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386381#comment-17386381 ] ASF subversion and git services commented on OPENMEETINGS-2640: --- Commit 6b15ae4598ddb946c6851b5fe15824eac1f9f365 in openmeetings's branch refs/heads/master from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=6b15ae4 ] [OPENMEETINGS-2640] slf4j tika, mysql, plugins > (7.0.0) Libraries should be updated > --- > > Key: OPENMEETINGS-2640 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2640 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 7.0.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 7.0.0 > > > Libraries should be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OPENMEETINGS-2593) (6.1.0) Library versions need to be updated
[ https://issues.apache.org/jira/browse/OPENMEETINGS-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385909#comment-17385909 ] ASF subversion and git services commented on OPENMEETINGS-2593: --- Commit ab193bb183d8c278f2a016bc151b9c88288d8a48 in openmeetings's branch refs/heads/java11-modules from Maxim Solodovnik [ https://gitbox.apache.org/repos/asf?p=openmeetings.git;h=ab193bb ] [OPENMEETINGS-2593] apache-parent, spring, kurento > (6.1.0) Library versions need to be updated > --- > > Key: OPENMEETINGS-2593 > URL: https://issues.apache.org/jira/browse/OPENMEETINGS-2593 > Project: Openmeetings > Issue Type: Task > Components: Builds >Affects Versions: 6.1.0 >Reporter: Maxim Solodovnik >Assignee: Maxim Solodovnik >Priority: Major > Fix For: 6.1.0 > > > Library versions need to be updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
