See: Description
Class | Description |
---|---|
BodyPart |
A mutable model representing a body part nested inside a MIME MultiPart entity.
|
BodyPartEntity | |
Boundary |
Utility for creating boundary parameters.
|
ContentDisposition |
A content disposition header.
|
ContentDisposition.ContentDispositionBuilder<T extends ContentDisposition.ContentDispositionBuilder,V extends ContentDisposition> |
Builder to build content disposition.
|
FormDataBodyPart |
Subclass of
BodyPart with specialized support for media type
multipart/form-data . |
FormDataContentDisposition |
A form-data content disposition header.
|
FormDataContentDisposition.FormDataContentDispositionBuilder |
Builder to build form data content disposition.
|
FormDataMultiPart |
Subclass of
MultiPart with specialized support for media type multipart/form-data . |
MultiPart |
A mutable model representing a MIME MultiPart entity.
|
MultiPartFeature |
Feature used to register Multipart providers.
|
MultiPartMediaTypes |
Convenience
MediaType (and associated String)
manifest constants. |
MultiPartProperties |
Injectable JavaBean containing the configuration parameters for
jersey-multipart as used in this particular application. |
Exception | Description |
---|---|
FormDataParamException |
A parameter-based exception for errors with
FormDataParam . |
Annotation Type | Description |
---|---|
FormDataParam |
Binds the named body part(s) of a "multipart/form-data" request
entity body to a resource method parameter.
|
The classes in this package provide for integration of
multipart/*
request
and response bodies in a JAX-RS runtime environment. The set of registered
providers is leveraged, in that the content type for a body part of such a
message reuses the same MessageBodyReader/MessageBodyWriter implementations
as would be used for that content type as a standalone entity.
For more information on the syntax and semantics of MIME multipart streams, see the following RFCs:
The following notes describe significant aspects of the implementation of the MIME MultiPart APIs in this (and related) packages:
The following list of general MIME MultiPart features is currently supported:
MIME-Version: 1.0
HTTP header is included on generated
responses. It is accepted, but not required, on processed requests.MessageBodyReader
implementation for consuming MIME
MultiPart entities. See below for usage restrictions.MessageBodyWriter
implementation for producing MIME
MultiPart entities. The appropriate Provider
is used to
serialize each body part, based on its media type.boundary
parameter on a
generated Content-Type
header, if not already present.multipart
, with the following
supported subtypes: alternative
, digest
,
mixed
, and parallel
.At present, the MessageBodyReader
implementation exhibits a
usability issue. It is not currently possible to know ahead of time what
Java class the application would prefer to use for each individual body part,
so an appropriate Provider
cannot be selected. Currently, the
unparsed content of each body part is returned (as a byte array) in the
entity
property of the returned BodyPart}
instance, and
the application can decide what further steps are needed based on the
headers included in that body part. The simplest technique is to examine
the received BodyPart
, and then call the getEntityAs()
method once you know which implementation class you would prefer.
The following list of general MIME MultiPart features is NOT (yet, in most cases) supported:
charset
parameter on the Content-Type
header
field. Currently, the hard coded charset is FIXME. [RFC2045#5.2]Content-Transfer-Encoding
header field. [RFC2045#6]message/*
family of content types.Copyright © 2007-2023, Oracle and/or its affiliates. All Rights Reserved. Use is subject to license terms.