The component has been removed in rev. 1763454 Thanks,
Jacopo On Wed, Oct 5, 2016 at 11:16 AM, Jacopo Cappellato < [email protected]> wrote: > On Wed, Sep 28, 2016 at 11:22 PM, Mike <[email protected]> wrote: > >> Great. So everyone seems to agree to dump oagis. Obviously someone took >> the time to create this component. My understanding it is used for >> automating B2B communication for purchase orders, inventory, etc. If you >> want ofbiz to play with the big boys, you need this TYPE of Electronic >> Data >> Interchange (EDI) functionality. >> >> So: If you want to dump oagis, please propose alternatives to make ofbiz >> integrate with EDI. All ERPs have this. >> >> > Thank you for the feedback Mike. > I do agree that providing some EDI functionality out of the box is very > important for an ERP system. OFBiz already has a few mechanisms for data > exchange that can be leveraged to implement specific or custom > integrations. The concept of an universal data interchange standard is > great, but, as far as I know, OAGIS has never reached the critical mass to > make it a viable solution for all integration needs. By experience I have > noticed that such standards tend to gain more tractions when they address > specific industries (e.g. parts interchange formats for the auto parts > aftermarket industry etc...). > Most importantly, when it was adopted by OFBiz, the OAGIS license allowed > us to include its xsd files; but after that, they have been relicensed > under an incompatible license: as a consequence this component is stuck to > an years old and unmaintained version making even more difficult to be used > to integrate with an external system. > > Kind regards, > > Jacopo > > >
