12-06-2013 05:20 PM - edited 12-06-2013 05:21 PM
This is for version 1.4.6 of the Java SDK.
While working with aim.Result I found the transaction to be null, which was unexpected. Taking a look aim.Result.createResult(...) I found that a deep copy of the transaction is made but the transaction field is never assigned, rather the transaction is assigned to target. This means that after creation the transaction field of a aim.Result instance will be null and the target field will reference the transaction.
Can anyone from AuthorizeNet confirm this a bug or if not explain the behaviour?