Obviously, this fails when any field has commas embedded (like my "Test Firm, Inc."), since the parser gets off (it thinks "Test Firm" is one field and "Inc." is the next) and then shows all subsequent fields in the wrong location in the responseMap.
Solved! Go to Solution.
Geez...why is it that you can look right at something and not see it, but the moment you write it up you find it? Thanks for the quick response anyway guys...before I could update my post you guys beat me to it.
There is still an issue with this...in the Java SDK net.authorize.data.cim.DirectResponse class there is a hardcoded comma delimiter:
public static final String RESPONSE_DELIMITER = ",";
So, if you change it in merchant interface to anything other than comma it'll still use a comma to tokenize - fail.
Luckily (or maybe unluckily), I've had to fix multiple issues with the Java SDK code so I just fixed this one too. My advice to anyone using the Java SDK - you might as well just import the source for it cause you're probably gonna need it...