No need to SHOUT 8).
The content of the message is dictated by the Packager, we will need to
see at least some of your CustomPackager definition is we are to
help/correct it.
I would think you have IFB_* field classes, and you might need IFA_*
flavours of them.
You should be checking that your Packager matches your 'Finacle' message
specification to ensure everything aligns - first.
--
Mark
> i tried same before also because of old class it was creating problem
> i deleted build file then rerun ant then it worked
ok, I don't see the issue, but you seem to be happy?
> but i am wondering but not tried yet can i use binary packager ie
> IFB_* and IFA_* in same packager? i meant some field have to send as
> binary like primary bit map then others like mti ,processing codes are
> to be send as ascii
You can have any mix of field classes within a packager you need so it
produces a message to match the interface you are talking to.
Each class independently works to pack or unpack the field it is given.
--
Mark
> i have not tried it because i have limited testing environment and i
> want to make sure before sending iso message to server
It sounds like you are trying to check that the message produced is what
your intended recipient desires.
Checking the interface specification against the Packager (and it's
fields) can be daunting when you don't know the field classes.
I would suggest you add a Logger to all components (Packager, Channel),
establish a test server (does the recipient provide such a test system)
that will present a port for your Channel at the basic level just a port
( netcat might be useful, but be careful how and where you use it), so
that you can see the 'send' process and check how each field type 'works'.
You could also run/debug the jPOS tests for the fields you are
interested in to see what packed data they produce.
--
Mark