[snip]
>
> Removing the operation part from the contract (because it's static in
> case of REST) means you only need to generate code for the different
> schemas (if you want to, which I'm firmly opposed to). There's tons
> of tools to do this (e.g. JAXB in Java) supporting XML Schema. Why
> would you need anything more if you fix the set of operations?
>
> Stefan
>
[snip]
This is the myth that REST is trying to promote IMO, the reality is
that the operations are not static, it is the MECHANISM which is
static, the operations remain exactly the same in both models.
By promoting a mechanism as a solution to a problem that is inherently
not about the mechanism is exactly why I think that REST v SOAP is
pointless.
To stress the point, a capability (operation) is something that has a
real-world effect, PUT, GET et al do not have a real-world effect
therefore are not in themselves operations from the perspective of
service or consumer.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
