GraphServiceException encapsulates a bit too much?

[kgarlikowski]

Currently there is not way to know i.e. what status code had been thrown by Graph API by inspecting com.microsoft.graph.http.GraphServiceException. That could be useful so that when calling GET on some Object we could catch the exception and actually know that 404 Not Found happened.

In the .Net Graph API SDK that seem to be possible, but Java version possibly hides too much of information regarding the error that caused it.

[darrelmiller]

That seems like a reasonable request. I'll have a conversation with the team to see if there are reasons why we didn't expose this information.

[darrelmiller]

Workitem 839917

[deepak2016]

@kgarlikowski Wanted to understand more on this issue. Do you mean that in com.microsoft.graph.http.GraphServiceException object we are currently not exposing any method to access responseCode and there should be a convenient method to access responseCode?
As I see there is a getMessage method in this object, which provides responseCode information as part of the message.

[kgarlikowski]

@deepak2016 Yes, totally. It would be great to have i.e. a responseCode exposed directly. It's somehow accessible via message, as you say, but we would need to have custom parsing logic which could easily fail when changes to message format happen.

try {
  serviceClient.users(user).buildRequest().get()
} catch (ex: GraphServiceException) {
  if (ex.responseCode == NOT_FOUND) ...

seems just much more convenient and less error prone.

[deepak2016]

This issue got fixed as part of pull request: #111
Changes have been checked-in to dev branch and should be available as part of binary in our next release.