> 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..