aspose file tools
The moose likes Web Services and the fly likes @pathparam and @queryparam Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "@pathparam and @queryparam" Watch "@pathparam and @queryparam" New topic
Author

@pathparam and @queryparam

simon tiberius
Greenhorn

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: 66
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: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: @pathparam and @queryparam
 
Similar Threads
How to make it generic?
question about REST
Argument passing in Restful webservices
Merge detached sub-class entity (JPA InheritanceType.SINGLE_TABLE) org.hibernate.WrongClassException
Payload in restful webservices