We are unable to retrieve shipping or billing information for one of our transactions due to a defect in the Java Reporting API.
The XML that we are receiving is missing the "customer" element, and as a result it is not falling into the
if(customer_list != null && customer_list.getLength() == 1)
block of code of the net.authorize.reporting.Results class so that the shipTo and billTo elements can be processed.
According to the authorize.net xml schema, the billto and shipto elements are not children of a customer element, so the java code should not require the customer element to be present before processing these records.
I will take a look at hacking together a solution that will get me by. Please let me know when I can expect a fix.
Quick follow up question. Is anyone else using the Java Reporting API? I've submitted three defects for it in the past two months, and none of them have been fixed yet. Is everyone working off of their own forked version of the code? Just trying to find out if there is a better way of getting these fixes pushed out to our customers.
Thank you for your help.