Replies: 5 comments 3 replies
-
Fully agree, that would be helpful. Since I want to keep using the regular RESTEasy Reactive rest client I am currently helping myself by using a
and making sure that the file has the desired filename. For us this seems to work as expected. |
Beta Was this translation helpful? Give feedback.
-
@Sopka I'm experiencing the same issue, have you found any solution to that? @sberyozkin please take a look. Might it be worth enhancing multipart file sending using rest-client-reactive? When you have |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
We faced it as well. I think it is quite common to read data from DB as byte[] (file data I mean) and it would be nice to be able to specify a name when we do upload. This |
Beta Was this translation helpful? Give feedback.
-
Just to make sure we are all on the same page, we are talking about specifying the filename when sending a multipart request using the Reactive REST Client, correct? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It is already documented how to send multipart messages in the official quarkus documentation at Sending Multipart messages.
With the old non-reactive version of the restclient implementation the filename could be set with:
The new reactive version is easier and only a PoJo is needed with a few annotations:
Corresponding RestClient:
Question: But how can you set the filename dynamically/programatically?
One possible solution/workaround has been mentioned in this issue: #26198
An implemented service is cumbersome to implement yourself without the
@RestClient
magic and looks then like:Beta Was this translation helpful? Give feedback.
All reactions