@pathparam vs @queryparam

[jmasta]

Hello everyone,

I was wondering if anyone knew the tradeoffs between using @queryparam and @pathparam. Let's say I have a call from the client:

uri = /rs/1/setup/cancelprogress?type=orange

and use a (@QueryParam "type") String type. How is this better, or worse, or that much different, from:

uri = /rs/1/setup/cancelprogress/orange

and use (@PathParam "type") String type, with @Path ("cancelprogress/{type}") on the method?

I've done a little reading, and I couldn't find why you would use one in one instance, and the other in another. I had someone tell me that in this case, I should use the @PathParam, but that was back when I was first starting development on this and I didn't think to ask why. I have mostly used @QueryParam for my needs.

Thoughts?