WebServices' Greatest Achilles Heel

Found this article via Collaxa's blog which says:

Integration is one of the most elusive goals of any organization. At a high level it seems easy to imagine the company as one large knowledge and information repository that can be tapped to answer any question necessary to make business function properly. But dig deeper and you find that one large repository is actually hundreds of systems, applications, files, and databases, some of which were written decades ago and haven't been updated since because the impact on the business of changing these legacy black boxes has become too severe. These systems run the business, but the business can't change them, either because they're written in some obscure language that uses shorthand and meaningless variable names to implement business rules, or because corporate memory has been erased and no one really knows how the programs do their work anymore. There's no way to make these monoliths interoperate with other programs, no way to get to the mythical single system of record. And so, instead of a vast repository of knowledge we have islands of inefficiency.
[...]
Web services, with abstract, business-oriented APIs reflecting business processes rather than technology processes, can be combined, redefined, and constantly adapted to changing business conditions. Business process management finally provides the tools and mechanisms for creating the agile organization.
And that's why Web services are important.

So lets just assume, for arguments sake, that WebServices is some magical technology where business process composition and therefore integration were painless. The Achilles Heel is that none of these "legacy black boxes" or "obscure languanges" have WebService implementations. WebServices are mostly implemented in the most modern environments like Java and .NET. Can anyone point me to a C binding for SOAP, or even a more difficult one that's implemented for Cobol?

So even if WebServices could fix all its foundational problems, its greatest Achilles Heel lies in its failure to solve what's most important, that is the integration of legacy systems.