I noticed that the client tries to execute a HTTP POST to the /attachments endpoint (line 103-111).
The attachments controller mounted onto that endpoint provides only two HTTP GET mappings (line 66 and line 76)
I do not understand how the attachment upload is supposed to work given that the endpoiint does not implement the verbs used by the client implementation
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
Last commit id on master (resource server): fe6d850b4f37b1f4eecd9f042d451
Last commit id on master (client) be212373f034117b4b430df977d0e5bd2e1fb62a
Description
There seems to be a mismatch between ReST client and server side implementation regarding atttachment upload
How to reproduce
While review the current master branch code for sw360/clients/client/src/main/java/org/eclipse/sw360/clients/rest/SW360AttachmentAwareClient.java and sw360/rest/resource-server/src/main/java/org/eclipse/sw360/rest/resourceserver/attachment/AttachmentController.java
I noticed that the client tries to execute a HTTP POST to the /attachments endpoint (line 103-111).
The attachments controller mounted onto that endpoint provides only two HTTP GET mappings (line 66 and line 76)
I do not understand how the attachment upload is supposed to work given that the endpoiint does not implement the verbs used by the client implementation
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
Logs
n/a
SW360 logs
n/a
Tomcat logs
n/a