globusrun-ws does not print all the nice explanations when e.g. a job
with staging fails due to an error in staging, but it did so in 4.0.x.

Gram4 in trunk puts all the fault information into the notification
message, as it did in 4.0.x. But due to changes in fault handling,
the fault causes are all nested, not arranged in an array.
(See "Faults" in
http://dev.globus.org/wiki/Java_WS_Core/Final_WSRF_Migration_Guide)

It looks like globusrun-ws grabs the description of the top-level fault
and ignores the descriptions in the nested FaultCauses.

I'll mark it critical, maybe it's a blocker.

I'll add links where to find examples, because attachments are disabled.