Web Services Making Software Coexist?

jgeelan writes "Despite the competitive uproar, coexistence of J2EE and .NET will be the norm and most sophisticated IT organizations will deploy on both development platforms. Who says so? No less an authority than the CTO of J2EE powerhouse BEA Systems, Scott Dietzen, writing in this month's Web Services Journal. Dietzen acknowledges that an ongoing conflict is in progress between Java and C# and between J2EE and the .NET server family and is refeshingly honest, admitting that "there is some truth to the 'write once, test everywhere' complaint against Java." His overall conclusion: ".NET is finding a sweet spot for programmed user interfaces, while J2EE continues to enjoy its sweet spot for server-side applications." Unusual honesty by someone so highly placed. Isn't this just what the software industry needs more of, in these increasingly interoperable times?"

Comments

Re:Honesty or idiocy?

[TummyX]

On a single platform, perhaps. It's true enough that early editions of Java's Swing weren't the swiftest UIs on the block, Swing has to contend with being platform independant. How well does a .NET UI run on a Solaris workstation?

The UI for most server-side applications is probably HTML, anyway, so I'm not sure what his point was.


That is the point. C#, ASP.NET and VS.NET are the perfect combination if you want to make HTML based UIs. You just drag a button onto a webpage, double click and write the event handling code in C#. The C# is compiled into a server side component along with some ASPX pages. The UI is completely HTML based and cross platform. The HTML generated can be transformed to work on all types of browsers (utilising the features of each). Anything that can't be done client side is done on the server side.

You pretty much write HTMl pages the same way you would write a standard GUI application and .NET takes care of the rest. Its a great way to program HTML UIs. And I think that was part of his point.

MS Model not ready for primetime?

[Otis_INF]

LOL :)

And why's that? WSDL isn't MS proprietry language, it's a standard defined by many companies, and should be used with UDDI, currently in v2.0. .NET is a framework which IS ready for primetime, because it offers all the functionality needed to build mission critical applications which have to serve thousands of users.

So, f00zbll, show me the beef where .NET falls short when it comes to delivering what's promised.

ps: I develop a lot of .NET software, I know what I'm talking about.