Skip to content
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

Closed
glassfishrobot opened this issue Mar 23, 2009 · 6 comments
Closed

ContentDisposition should be part of JAX-RS #13

glassfishrobot opened this issue Mar 23, 2009 · 6 comments
Milestone

Comments

@glassfishrobot
Copy link

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

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by imyousuf@java.net

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Issue-Links:
duplicates
JAX_RS_SPEC-348

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
@mpotociar said:
Closing as duplicate.

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Marked as duplicate on Thursday, February 7th 2013, 12:28:02 pm

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA JAX_RS_SPEC-8

@glassfishrobot
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant