etf.org/rfc/rfc2388.txt">RFC 2388 for the formal definition of this media type.
For a server side application wishing to process an incoming multipart/form-data
message, the following features are provided:
- Incoming entities will be of type {@link FormDataMultiPart}, enabling access to the specialized methods.
- Incoming body parts will be of type {@link FormDataBodyPart}, enabling access to its specialized methods.
- Convenience method to return the {@link FormDataBodyPart} for aspecified control name.
- Convenience method to return a
Map
of {@link FormDataBodyPart}s for all fields, keyed by field name.
For a client side application wishing to construct an outgoing multipart/form-data
message, the following features are provided:
- Media type of the {@link FormDataMultiPart} instance will automaticallyset to
multipart/form-data
. - Builder pattern method to add simple field values as body parts of type
text/plain
. - Builder pattern method to add named "file" field values with arbitrary media types.
FIXME - Consider supporting the use case of a nested multipart/mixed
body part to contain multiple uploaded files.