Marek,
> - perhaps it is my misunderstanding, but I don't agree that JAX-RS
> resource classes should be tied to resource entities.
> Perhaps it was an unfortunate choice of the name, but JAX-RS resource
> classes are conceptually controllers, not models.
I understand you view, but yes, the name is the problem. A resource is a model object, not a controller object. If you address
http://foo/bar, you expect bar to be a model object (a document), not a controller (a web server software). But a second point is that in many cases we noticed that making resources as models is beneficial. I understand MVC and other layer models, but sometimes "real-world OOP" is superior. In the case of linking other entities for example. See, if there is a bar in foo (like above) and I want to link that but don't know the URL, I can just set @Linkable to the FooBar resource. If you do not make resources as models, you cannot do that -- and have to invent a strange wheel, as http was never intended to be MVC...
Regards
Markus