Its ok to use query parameters as long as they are part of the identity
of the resource. IMO, don't use them to modify a resource. Instead
pass a representation with your POST.
On 2/1/2013 3:34 AM, Denica Gencheva wrote:
> On 01/02/2013, Nuwan Bandara wrote:
>> Hi,
>>
>> I have a RESTeasy web
On 01/02/2013, Nuwan Bandara wrote:
> Hi,
>
> I have a RESTeasy web service. It accept POST requests. As an example
> client will call the web service like this
>
> http://localhost:8080/n-tweb-comm-war/ws/updateResultIndicator;accessionNumber=1;analyteCode=2;workstation=3;siteCode=4;testIndicator
I would do something like
http://localhost//results/
Post your data as URL form encoded data. Any client should do this for you
with a setParameter("accessionNumber", 1) style call. Your resources should
take those params as @FormParam("accessionNumber") Long accessionNumber
If the call is meant
Hi,
I have a RESTeasy web service. It accept POST requests. As an example
client will call the web service like this
http://localhost:8080/n-tweb-comm-war/ws/updateResultIndicator;accessionNumber=1;analyteCode=2;workstation=3;siteCode=4;testIndicator=5;testStatus=66
My question;
1. is this a
