[2.1.0-SNAPSHOT] QMUX support for per-MTI mapping and response validation

[Alejandro Revilla]

For those of you not on the jPOS Slack, 

FTW, this commit (https://github.com/jpos/jPOS/commit/73ace32dafb61551aef26d0b6c7dd1da4d9256c0) allows per MTI QMUX override.

We have a situation where 800-type messages are used to re-sync the STAN, so a 0800 with a STAN=0000001 would get a reply with STAN=xxxxxx, xxxxxx being the STAN the terminal was supposed to send in first place. In those messages, we need to use a different key on 0800s but revert to the default key (i.e. 41+11) for other messages. The configuration is easy:

<qmux>

   ...

   ...

 <key>41,11</key>

 <key mti="0800">41</key>

</qmux>

In a follow-up commit (https://github.com/jpos/jPOS/commit/aac64d370029b4696245722378e8ef1ca86d9138) we are also making sure that a response has actually a valid response MTI. We found situations where a host would reply a 0200 with another 0200 (in their mind that would be a 'reject', but QMUX was handling it back to the application as a response to the original 0200). Most applications validate that, but just in case, we wanted to stop it at the MUX level as a safety net.

PS.- A nightly build has been forced

PPS.- For a complete list of changes, see http://jpos.org/wiki/ChangeLog

--

@apr