In bug #1065270 we replaced the external Ruby layer for EDI parsing with an internal Perl parser. Given some recent complications with installing the Ruby dependencies (Bug #1342227) AND given that removing the Ruby layer entirely would simplify installation and maintenance... Maybe now is the time to kill it.
To remove it, we need only to be able to produce EDI ORDER records natively in Evergreen. Currently for orders, we generate JEDI, a custom JSON representation of EDI. The Ruby layer translates the JEDI to EDI. Instead of doing this, we could just produce EDI text instead from a new action/trigger template, then skip the Ruby translation.
Once the A/T event produces EDI, edi_pusher can skip the ruby step and push the output directly to the vendor.
I've done some simple proof of concept work on this. Working branch forthcoming.
Code in progress. It's not ready for use (or human eyes).
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1373690- acq-order- edi