Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 1.3-rc1
    • Fix Version/s: None
    • Component/s: Modules: (other)
    • Labels:
      None
    • Similar Issues:
      MULE-7892Enable testing mode in functional tests
      MULE-4806REST functionality of MuleRESTReceiverServlet is non-functional
      MULE-7784Configure build for skipping functional tests
      MULE-7483Make MEL functions null-safe
      MULE-7113Add selectors functionality on Watermark
      MULE-9Functional tests for all providers
      MULE-7132wilcard function for mel
      MULE-8233Move tests/functional tests to tests/integration
      MULE-7525Ajax mule.rpc always calls first invoked function
      MULE-1022Improvements to functional / integration tests

      Description

      EDI/EDIFACT (Electronic Data Interchange, see http://en.wikipedia.org/wiki/Electronic_Data_Interchange) functionality is an interesting feature for any ESB in B2B settings. This issue is meant as initial starting point to collect ideas and contributions.

        Activity

        Hide
        kenneth westelinck added a comment -

        Since I have 4 years of experience in EDI (Edifact and X12) I think I might be able to help. In projects, I have already succesfully used (in java based projects):

        The problem with EDI is:

        • Sure you can write something that can parse/convert this type of files
        • You will need some kind of partnermanagement (who is sending orders to who)
        • You will have to be able to validate incoming and outgoing EDI (supported by tools mentioned above)
        • You will need support for batching/de-batching. One EDI document might contain multiple orders or invoic messages (or a combination).
        • You will need support for functional acknowledgements. This is not popular in the Edifact world, but is definetely used in X12 (997 documents).
        Show
        kenneth westelinck added a comment - Since I have 4 years of experience in EDI (Edifact and X12) I think I might be able to help. In projects, I have already succesfully used (in java based projects): OBOE ( http://www.americancoders.com/OpenBusinessObjects/): This is an API and XML convertor for EDI (both X12 and Edifact). As far as I know, this is the beste implementation out there, but it's not free. XML-Edifact ( http://www.xml-edifact.org/): This is a perl library to convert Edifact to XML and vice versa (no support for X12) The problem with EDI is: Sure you can write something that can parse/convert this type of files You will need some kind of partnermanagement (who is sending orders to who) You will have to be able to validate incoming and outgoing EDI (supported by tools mentioned above) You will need support for batching/de-batching. One EDI document might contain multiple orders or invoic messages (or a combination). You will need support for functional acknowledgements. This is not popular in the Edifact world, but is definetely used in X12 (997 documents).
        Hide
        henk-jan ebbers added a comment -

        You might want to look at Bots (http://bots.sourceforge.net).
        I handles EDIFACT, XML, CSV, flat file; X12 is being worked on.
        It is written in python.

        Show
        henk-jan ebbers added a comment - You might want to look at Bots ( http://bots.sourceforge.net ). I handles EDIFACT, XML, CSV, flat file; X12 is being worked on. It is written in python.
        Hide
        Ross Mason added a comment -
        Show
        Ross Mason added a comment - This can be tracked on MuleForge: http://www.muleforge.org/projects.php?projectname=EDI%20Reader

          People

          • Assignee:
            Ross Mason
            Reporter:
            Holger Hoffstaette
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development