I have worked on Java projects (J2EE integration layer) as well as webMethods projects and in my experience i found that Java falls short in providing out of the box connectors (adapters) and it involves more man hours and effort to get an interface up and running in Java compared to webMethods. Also, it is not as flexible as what an EAI implementation can provide (BAM,BPM, SOA, ESB, Deployer, TN etc ). Of course now a days there are third party softwares that can provide this functionality (PEGA etc) but again that adds additional cost and code management.
On the other hand, if it is a relatively small implementation (does not involve external partners) then Java would be more suitable because of high licensing fees of the EAI softwares. So far, i did not see or heard a successful Java Integration at an Enterprise Level (or as an ESB) with out cost over runs or a good Architecture.
Again, This is just my experience and I might not have seen enough. Others, any thoughts?
Cheers,
Akshith
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods