AppSpecific mapping problem in TypeManager.java

Aug 29, 2012 at 4:19 PM

There appears to be a bug in R1.3.1 of the Health Vault Java SDK.

I successfully managed to write AppSpecific data to Health Vault (verified it using the Microsoft web interface) but having issues retrieving it and I think it's a bug in the com.microsoft.hsg.thing.oxm.jaxb.thing.TypeManager class.

Using thing.getData() for an AppSpecific type ID, I received a NullPointerException in Thing.java. It appears that the "String[][] types" array in TypeManager.java is referencing the wrong class for the AppSpecific type ID. The mapping shows:

     {"a5033c9d-08cf-4204-9bd3-cb412ce39fc0", "application.Application"},

however the actual class name in the com.microsoft.hsg.thing.oxm.jaxb.application package is "AppSpecific". 

The Fix:

I changed the line above as follows and it seems to be working:

     {"a5033c9d-08cf-4204-9bd3-cb412ce39fc0", "application.AppSpecific"},

Can this be updated in the SDK?

Thanks!!

Coordinator
Sep 6, 2012 at 3:36 PM

Thanks for the heads up.  I'll get this fixed.

Sep 8, 2012 at 8:00 PM

Thanks!