StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19392455
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-15T22:52:21.767
FavoriteCount
0
LastActivityDate
2013-10-15T22:52:21.767
LastEditDate
LastEditorUserId
0
OwnerUserId
254061
ParentId
19315263
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
It seems you are doing things by "hand". I would recommend you0 give a try to <a href="http://cxf.apache.org/" rel="noreferrer">Apache CXF</a>. It's a neat implementation the JAX-RS API that enables you to almost forget about REST. It plays well with (also recommended) Spring. You simply write classes that implement your interfaces (API). What you need to do is to annotate the methods and parameters of your interfaces with JAX-RS annotations. Then, CXF does the magic. You throw normal Exceptions in your java code, and then use exception mapper on server/nd or client to translate between them and HTTP Status code. This way, on server/Java client side, you only deal with regular 100% Java exception, and CXF handles the HTTP for you: You have both the benefits of a clear REST API and a Java Client ready to be used by your users. The client can either be generated from your WDSL, or built at runtime from introspection of the interface annotations. See : <ol> <li><a href="http://cxf.apache.org/docs/jax-rs-basics.html#JAX-RSBasics-Exceptionhandling" rel="noreferrer">http://cxf.apache.org/docs/jax-rs-basics.html#JAX-RSBasics-Exceptionhandling</a></li> <li><a href="http://cxf.apache.org/docs/how-do-i-develop-a-client.html" rel="noreferrer">http://cxf.apache.org/docs/how-do-i-develop-a-client.html</a></li> </ol> In our application, we have defined and mapped a set of error codes and their counterpart Exceptions : <ul> <li>4XX Expected / Functional excecption (like bad arguments, empty sets, etc)</li> <li>5XX Unexpected / Unrecovable RunTimeException for internal errors that "should not happen"</li> </ul> It follows both REST and Java standards.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POError Handling on Java SDK for REST API service
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRaphael Jolivet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.