With the two major SOAP camps, .NET and J2EE working towards a compliant operating language, what if you choose .NET and find out J2EE becomes the best of breed, but only on their platform?
Let's face it -- the PDA market still has a major hold on the retail market and we are missing supported applications for CE 3.0+++.
Help clear up the smoke.
(I'm not sure what you mean when you refer to "their" platform in regards to J2EE. J2EE runs on most platforms, although probably not on a PDA. In any case, J2EE runs very well on Win32, Linux, and many flavors of Unix.)
But you don't need to make an all-or-nothing choice between .NET and J2EE. SOAP is vendor- and platform-neutral. You should choose a SOAP implementation based on the requirements of your application -- for each application. What language are you working with? What platform do you want to run it on? What existing infrastructure do you need to support? What other constraints do you need to deal with (footprint, performance, scalability, reliability, security, etc.) These questions should guide you to your choice.
In general, I recommend using .NET when you're working with VB, C#, Excel, IIS/ASP, or any other Microsoft languages/technologies. If you're using Java, your choices are much wider, so you probably want to look at characteristics such as ease of use, performance, configuration fit, portability, etc. For a WinCE PDA application, you might try PocketSOAP or Systinet WASP for C++
Dig Deeper on Topics Archive
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading