[jpos-users] Non-ISO message handling

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[jpos-users] Non-ISO message handling

jayadeep.cse
Hi All,

I need to implement the non-ISO messages. The message format is like TPDU followed by TLV message. The message format is like

60035400000001000430323030000200053032303030

600354000=>TPDU
0001=>TAG 1
0004=>Length(4 bytes)
30323030=>Value

0002=>TAG 2
0005=>Length(5 bytes)
3032303030=>Value.

FSDMsg will not be applicable here as the message is not fixed length or field separated.  Defining a bitmap less generic packager (emitBitmap='false') with IF_NOP as field 0 is also not feasible as the length of the field is variable and I do not get this length in the message.

Is there any way in the jPOS to achieve this?

Thanks,
Jayadeep 

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/534d1451-5a98-4df4-acb9-78a4f48df7dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [jpos-users] Non-ISO message handling

A Haris Kurniawan
Victor will probably say... Create your own isofieldpackager, modify setheader and getheader on the channel :D. 

On Feb 9, 2017 9:34 AM, "jayadeep.cse" <[hidden email]> wrote:
Hi All,

I need to implement the non-ISO messages. The message format is like TPDU followed by TLV message. The message format is like

60035400000001000430323030000200053032303030

600354000=>TPDU
0001=>TAG 1
0004=>Length(4 bytes)
30323030=>Value

0002=>TAG 2
0005=>Length(5 bytes)
3032303030=>Value.

FSDMsg will not be applicable here as the message is not fixed length or field separated.  Defining a bitmap less generic packager (emitBitmap='false') with IF_NOP as field 0 is also not feasible as the length of the field is variable and I do not get this length in the message.

Is there any way in the jPOS to achieve this?

Thanks,
Jayadeep 

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/534d1451-5a98-4df4-acb9-78a4f48df7dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAL8bJ0FcDry030BgwWoXAjLeCXcKNMWaWJBtp1Fw6dRqCwyQJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.