[regrep-comment] REST Exception Handling should be more descriptive.

[Uday Subbarayan <uday.s@sun.com>]

Comments About: OASIS/ebXML Registry Services Specification v2.2 /
                             6.6.5 Exception Handling in REST Binding

It would be nice if the REST Exception handling is more descriptive about
the Http error codes. Right now it says apropriate error codes & messages
should be send back to the client.

For example, in the QueryManager Get Request,
GET /rest?interface=QueryManager&method=getRegistryObject&param-id=urn:uuid:a1137d00-091a-471e-8680-eb75b27b84b6
HTTP/1.0 680

What would be the best error code, if:
1.interfaces == null || interfaces.equals("") OR
2.interfaces.equalsIgnoreCase("LifecycleManager") OR
3.interface equals something else....

and the same goes for if we go 1 level down with "method" and another level
down to "param-id"
Similarly for the POST request for all the "LifeCycleManager" interface.

There is only 1 example for the "ObjectNotFound" and simarly the spec should
be more descriptive about the Http error codes for rest of the use cases.

Thank you,
-Uday Subbarayan.
uday.s@sun.com
Contributor to http://ebxmlrr.sourceforge.net/contributors.html