Issue 78

* unrelated javadoc updates in metadata parser
* added 'rest' to root error context to make clear which instance of command is used (where multiple exist with same simple name)
* updated error creation on generic failure to include full stack trace as message
This is building the response to the client.  It's probably more useful to report the stack to the client so they can include it in any defects/issues.  Otherwise, we have to reproduce to get the stack from server logs.

----- Original Message -----
> > @@ -296,7 +296,7 @@ public Response delete(DeleteRequest req) {
> >              response.getErrors().add(e);
> >              response.setStatus(OperationStatus.ERROR);
> >          } catch (Exception e) {
> > -            response.getErrors().add(Error.get(CrudConstants.ERR_CRUD,
> > e.toString()));
> > +            response.getErrors().add(Error.get(CrudConstants.ERR_CRUD,
> > e));
> 
> All the other methods doesnt seem to use the logger, we may need this
> (tracing a bug, which in the current state we would just have the last
> message, an a couple of nested exceptions could have occurred ). I comment
> just this line but the same concept apply to all methods (and maybe other
> places as well I think). Below I comment an usage of the logger (which I was
> expecting)
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/lightblue-platform/lightblue/pull/101/files#r16271935