Skip to content
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.

204 No Content causes an exception #73

Open
glassfishrobot opened this issue Sep 22, 2014 · 3 comments
Open

204 No Content causes an exception #73

glassfishrobot opened this issue Sep 22, 2014 · 3 comments

Comments

@glassfishrobot
Copy link
Contributor

In the event of a 204 No Content response on a POST, PUT or DELETE the client will throw a UniformInterfacEexception. Why is this?

@glassfishrobot
Copy link
Contributor Author

Reported by litemode

@glassfishrobot
Copy link
Contributor Author

sirgeek said:
A 200 is a "success", What you may want to do is modify your WADL file

Change your line that has:

wadl:response (or <wadl:response status="200"> )
<wadl:representation mediaType="text/xml" element="cts:OrganizationList" />
</wadl:response>

to

<wadl:response status="200 204">
<wadl:representation mediaType="text/xml" element="cts:OrganizationList" />
</wadl:response>

@glassfishrobot
Copy link
Contributor Author

This issue was imported from java.net JIRA WADL-73

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

No branches or pull requests

2 participants