This article covers interoperability between the Microsoft.com Web service, built with Web Services Enhancements 1.0 SP1 for Microsoft .NET, and a Java client. See how the WS-Security specification and implementation can be used to validate a Web service call from Java to Microsoft .NET. GLUE 4.1.2 Professional from webMethods will be used to enable WS-Security functionality for the Java client.
Java/.NET Interoperability with the Microsoft.com Web Services
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
You gotta admire the consistency of MS. Here’s another fine example of recruiting developers, the logic being that if they take the time to learn to interoperate they will also take the time to learn .Net properly and a percentage will move over to its as primary platform.
The puzzle is why Sun is not doing the same.
The puzzle is why Sun is not doing the same.
They might be, but because this site is MSDN Jr, it will never be linked here.
Hey, a new preview options! Hurray!
… Java client
(At lease there is somebody doing it !)
By the way, they must be realy missing customer to start advertising for “compatibility” stuff !
I remember the time when MS lauch .net and balmer claimed : “It is a revolution” and “has nothing to do with Java” !
Now people are used to .net, and they now : It is 99% Java like and it is definitively not a revolution if you already are playing with Java.
The situation is pretty bad for MS has the hype is over
Now they “try” to recrut java coders ?
Who on earth is willing to lock again on MS only platform without any major benefit when you are used for years to quickly switch from one platform to another ?!?
“Poor” MS, alone on their own platform, at least they can spend few other billions to sponsorize for another couple of years more “click&develop” ads on TV chan for they .net 😉
My wife is a Java developer at a company that has one of the hugest IT departments in the world. Her group has just started doing .NET development using C#. They got rid of all the front end code they did in Java and developed the front end in .NET and using the mobile .NET framework for the PDA’s. They use Java on the back end. The reason for them getting rid of Java on the front end was it sucked. They spent over two years trying to get it to work well, rewrote the entire thing in less than 6 months in C# and the users love it. This is a good example of having .NET and Java work together. They saw the shortcomings and used the best tool for the job.