https://community.developer.cybersource.com/t5/Integration-and-Testing/AIM-Java-SDK-Potential-Bug-with-AIM-Result/m-p/37241#M20649 <P>This is for version 1.4.6 of the Java SDK.</P><P>&nbsp;</P><P>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.</P><P>&nbsp;</P><P>Can anyone from AuthorizeNet confirm this a bug or if not explain the behaviour?</P><P>&nbsp;</P><P>Thanks,</P><P>&nbsp;</P><P>Harlan</P> Sat, 07 Dec 2013 01:21:17 GMT harlan 2013-12-07T01:21:17Z https://community.developer.cybersource.com/t5/Integration-and-Testing/AIM-Java-SDK-Potential-Bug-with-AIM-Result/m-p/37241#M20649 <P>This is for version 1.4.6 of the Java SDK.</P><P>&nbsp;</P><P>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.</P><P>&nbsp;</P><P>Can anyone from AuthorizeNet confirm this a bug or if not explain the behaviour?</P><P>&nbsp;</P><P>Thanks,</P><P>&nbsp;</P><P>Harlan</P> Sat, 07 Dec 2013 01:21:17 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/AIM-Java-SDK-Potential-Bug-with-AIM-Result/m-p/37241#M20649 harlan 2013-12-07T01:21:17Z