New critical article on JAXRPC/WSDL etc.
Koshuke wrote (while the forum was done this morning) in an e-mail to me:
... I agree with some of their criticism --- like the complexity in O/X mapping --- but I'm disappointed that their solution to the problem is:
If a WSDL/XSD description of an Alpine-hosted service is
required, the user will be required to write it
So, their approach is "this is a hard problem, so let's stop solving it".
I agree with Kohsuke, forcing developers to deal with the sheer complexity of schemas and wsdl will kill this project. The authors seem to know that, so at the end, they prepare the reader for another radical idea: "let's invent a new language (Cw or whatever MS is cooking there), where SQL and XMl stuff (tables, result sets, nodes) are first class citizens like ints and longs". Sounds too Groovy :-)