You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if this software is usable without a compilation phase for the following purpose.
We have to exchange a lot of different record types ( > 300 ) between a Cobol mainframe and a distributed platform.
Ideally we would make this configuration driven for any new format, without generating new Java classes.
Is this possible : Copybook-record ==> program-reading-a-cobol-data-structure ==> XML or JSON ?
So far I didn't find any way around this compilation phase that for every new record format, we need to generate new classes.
The text was updated successfully, but these errors were encountered:
I was wondering if this software is usable without a compilation phase for the following purpose.
We have to exchange a lot of different record types ( > 300 ) between a Cobol mainframe and a distributed platform.
Ideally we would make this configuration driven for any new format, without generating new Java classes.
Is this possible : Copybook-record ==> program-reading-a-cobol-data-structure ==> XML or JSON ?
So far I didn't find any way around this compilation phase that for every new record format, we need to generate new classes.
The text was updated successfully, but these errors were encountered: