-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ContentDisposition should be part of JAX-RS #13
Milestone
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Content-Disposition plays a important role in multipart form data and with
many use cases of multipart form data in RESTful WS, it would make JAX-RS more
portable if ContentDispostion like API (currently an example is available in
jersey-core module) is made part of JAX-RS, as it would reduce dependency from
implementor. In fact, with the usages I have faced this is one of area where I
have to depend of Jersey directly instead of JAX-RS.
Environment
Operating System: All
Platform: All
The text was updated successfully, but these errors were encountered: