Is it likely that one group in an organization can go off and write a bunch of stuff in Java with IBM Visual Age, another group in the same organization go off and write a different bunch of stuff in C# with Visual Studio .NET...

... and then expect the two projects to successfully communicate and "play nice" with each other?

Is it likely that one group in an organization can go off and write a bunch of stuff in Java with IBM Visual Age, another group in the same organization go off and write a different bunch of stuff in C# with Visual Studio .NET...

one group in an organization can go off and write a bunch of stuff in Java with IBM Visual Age, another group in the same organization go off and write a different bunch of stuff in C# with Visual Studio .NET... ... and then expect the two projects to successfully communicate and "play nice" with each other?

Test both web services and web services clients with the WS-I testing tool and be sure there won't be any integration problems.

Lots of things become clear, when you stop thinking /Viktor Pelevin/

J. Acc.

author
Ranch Hand

Posts: 33

posted 13 years ago

As long as both .NET and Java Web services conform to the same set of open standards (primarily WSDL and SOAP) and the same versions of these standards, there should be no real problems with enabling cross-platform communication. Using WS-I profiles is a useful way of guaranteeing this conformance of both end. The ability to cross proprietary platforms with a vendor-neutral communications framework is the main reason Web Services have become so significant.