I am really impressed with the level of informed debate over on this thread
. However given the date of the discussion (before .NET was released), I wonder if it would be relevant to ask the question again, considering .NET is now more mature?
Our company is currently considering questions similar to those in the original thread, so I'm looking for input to help us.
We currently have older apps running under the VB6/COM/MTS model, and are considering our upgrade paths.
I've done a bit of research, and am a competent Java and C# developer, but have not done any J2EE n-tier or .NET web-services type work, so I'm open to suggestion. Specifically I keep reading that J2EE offers benefits in state-management and persistence. How does this translate to real-world benefits to the programmer on the ground?
I'm reasonably confident that I understand the platform implications, from MS licensing, and also under J2EE, with free (JBoss), intermediate (Orion), and big-iron (Websphere), options, but am open to comments on that front also.
If it helps, our environment is financial services, and our high-level requirement is basically a distributed environment allowing querying and maintaining of client accounts. E.g. online balance enquiries, local maintenance apps running against semi-remote databases, etc.