On Aug 10, 2009, at 9:31 AM, Felipe Gaścho wrote:
> ok, I will review this option..
>
> perhaps:
>
> PUT - insert (create)
PUT can be used for create and *complete* update. For create it
requires that the client knows the URI of what newly created resource
should be.
> POST - update
If you are doing a partial update then POST can be used. If you are
doing a complete update then use PUT.
Paul.
> GETs.. - select
>
> for thsi project I guess I won't have several POSTs and PUTs in a same
> resource.......
>
> 2009/8/10 Felipe Gaścho <fgaucho_at_gmail.com>:
>>> but why require the "create" ? unless you require POST on "user"
>>> to mean
>>> other things.
>>
>> humm.. yes, I can do like that - to follow the strict rest style..
>> but:
>>
>> I am exposing my domain model through the service interface, so my
>> Java classes contains several resources at once - each class
>> regarding
>> each entity... so a same Java class may contains several POSTs and
>> PUTs methods..
>>
>> several times I tought about that and finally I realize that creating
>> a new resource just to split business logic from entity crud was
>> perhaps too pedantic..
>>
>> but I don't have a strong position about this..
>>
>
>
>
> --
> Looking for a client application for this service:
> http://fgaucho.dyndns.org:8080/footprint-service/wadl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>