Update of PR #2300

[tenthe]

Purpose

This PR is an update of #2300. I could not push my changes to the other PR.
Therefore I created a new one.

I had to merge the new HTTP API into the branch. @muyangye can you please check if this is correct?

Remarks

PR introduces (a) breaking change(s): no

PR introduces (a) deprecation(s): no

[muyangye]

@tenthe Thanks a lot for merging🙏.

Is there any reason to switch from JAX-RS to Spring MVC? I copied the code to local and was not able to compile it because endpoints in PipelineElementFile.java expect a return of type ResponseEntity which is part of Spring MVC whereas the actual return is of type Response which is part of JAX-RS. Other than that I spot no issues.

[tenthe]

Hey @muyangye,
thanks for trying it out.

What exactly didn't work for you?
I just tried to upload two files with the same name and I was able to change the name of the second file.
My last commit only fixes some linting errors.

The change from JAX-RS to Spring MVC was made to harmonize our code base, see #2276.
If the change causes problems in your development setup just let me know and we can try to solve it together.

[muyangye]

Hey @muyangye, thanks for trying it out.

What exactly didn't work for you? I just tried to upload two files with the same name and I was able to change the name of the second file. My last commit only fixes some linting errors.

The change from JAX-RS to Spring MVC was made to harmonize our code base, see #2276. If the change causes problems in your development setup just let me know and we can try to solve it together.

@tenthe Thanks for pointing out the harmonization PR. I wasn't able to do git pull or git push so I didn't get the latest change brought by #2276. After manually downloading the dev branch to local I was able to compile and everything works perfectly. Let's merge this PR and I'll continue the work on #2181 once I return to USA since I have network issue with git right now.