You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume we definitely want to support this, for the platform-http to be on par with the older HTTP components.
The question is how to implement that. The older components use AttachmentMessage from camel-attachments to store the uploaded files. camel-attachments depends on javax.activation.
(a) The "easy" solution: pull camel-attachments and javax.activation as dependencies, and do not care for the increase of the app size caused by that.
(b) The "optional" solution: provide some no-op handling of file uploads by default that does not depend on camel-attachments and javax.activation. Handle the uploads properly via camel-attachments (wrapped in an extension) and javax.activation only if the user adds them as deps.
(c) ?
Is the work associated with (b) worth the benefits it might bring?
The text was updated successfully, but these errors were encountered:
I assume we definitely want to support this, for the
platform-http
to be on par with the older HTTP components.The question is how to implement that. The older components use
AttachmentMessage
fromcamel-attachments
to store the uploaded files.camel-attachments
depends onjavax.activation
.(a) The "easy" solution: pull
camel-attachments
andjavax.activation
as dependencies, and do not care for the increase of the app size caused by that.(b) The "optional" solution: provide some no-op handling of file uploads by default that does not depend on
camel-attachments
andjavax.activation
. Handle the uploads properly viacamel-attachments
(wrapped in an extension) andjavax.activation
only if the user adds them as deps.(c) ?
Is the work associated with (b) worth the benefits it might bring?
The text was updated successfully, but these errors were encountered: