This week's book giveaway is in the Big Data forum.
We're giving away four copies of Elasticsearch in Action and have Radu Gheorghe & Matthew Lee Hinman on-line!
See this thread for details.
The moose likes Web Services and the fly likes @pathparam and @queryparam Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Elasticsearch in Action this week in the Big Data forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "@pathparam and @queryparam" Watch "@pathparam and @queryparam" New topic

@pathparam and @queryparam

simon tiberius

Joined: Oct 30, 2012
Posts: 29
I want my URI to look like this for read operation:

let's say the customer id is 147 and I want to view 10 of his orders starting from the 30th order, the URI will look llike this:

is this RESTful? and how do I parse the params?

is this the correct RESTful implementation of read operation? thanks
sandeeprajsingh tandon
Ranch Hand

Joined: Mar 06, 2009
Posts: 74
I DONT think its UNRESTFUL..but if i was you, i would have rather passed an Object called OrderDetails and obtained my parameters from there.That way the URI would be a little more clean and i use POST.
I agree. Here's the link:
subject: @pathparam and @queryparam