I'm still banging my head on the wall about the EAI problem. It almost seems if you use web services for EAI, you're moving back to the EDI model. Since in EDI, the sender flattens the data out to a certain format, sends it across to the receiver who "unflattens" it. With web services it seems like it's the same thing except using XML as the format. Where is the value-add? The adapter folks (Tibco, Crossworlds, etc.) would advocate the outbound adapter (sender) "normalizing" the data into a format known to the transport which maps that into the receivers desired format. The advantage being here that many required changes can be absorbed at in the middle transport layer. But these architectures usually require
alot of work. I would just like to know if others have any idea where EAI is going and will it get any easier?
(thanks in advance)