Generally yes, I agree that it is useful to provide the cause in **some** cases, but not so much in the case of StudioConnection.java, line 136. My original idea was that we throw a SUSEStudioException if we either:

- find one of the known error codes in the response -> no Throwable cause is required since there is none
- we catched some other checked exception that we want to wrap -> no error code required since there is none

So I would vote for removing the additional constructor for now, if you don't mind, and change StudioConnection.java to just re-throw the occurring SUSEStudioException for example. We also should not wrap a SUSEStudioException into another one I think.