J2E and .Net Differences?

I have to write up a 2 page simple paper on the advantages and disadvantages to using each and what are the differeces?

Could anyone help me out. This is for a job

http//www.learningcircuits.org/2003/jun2003/aldrich.htm
http//www.javaworld.com/javaworld/jw-03-2002/jw-0308-j2eenet.html
http//www.ftponline.com/wss/2002_10/magazine/columns/webservices/
http//blogs.msdn.com/mohammadakif/archive/2005/11/15/493161.aspx

I could do this for you, but I do not DO other people's work for them - unless of course we both work for the same company. So there are a few good websites to read on, and I am sure you can easily get 2 pages of information from that.

You the man

All I did was go to google.com and search for J2E and .Neturl==http://=http:///url Differences?

And it offered to change it to J2EE and .Neturl==http://=http:///url Differences?

And those are some of the top sites.

But you are welcome.

It's J2EE, not J2E (hence the Google correction).

The differences are wide and varied, and have extremist followers in both camps that will not tolerate any viewpoint from the other side, so good luck finding an unbiased opinion.

Without indicating a preference for either (although I'm sure I have in the past when talking about what I do for a living), I'll boil it down to this simple philosophy

[i9e800242b5]J2EE is a [b9e800242b5]language-dependant, platform-independant[/b9e800242b5] development solution, while .NETurl==http://=http:///url is a [b9e800242b5]language-independant, platform-dependant[/b9e800242b5] development solution.[/i9e800242b5]

How important either of those are to any given developer or company is dictated by the type of systems in use. For example, companies with a heterogenous systems profile including mainframes, linix servers, Windows servers/desktops, embedded systems, etc., all running a variety of operating systems, who want the obvious benefit of having all developers speaking the same language, are better served by Java/J2EE. OTOH those companies/developers who are strictly Microsoft-centric, from the lowest handheld/embedded platform to the biggest Windows Server cluster, might better be served by .NET,url==http://=http:///url since they don't have to worry about supporting non-Microsoft platforms. Regardless of what a lot of laymen or non-IT types might believe, there are many, many non-MS systems being used in the world today. In fact with most larger corporations and research/educational institutions, outside of simple desktops, I'd say that Microsoft platforms are probably still in the minority.

Note that I'm discounting Mono from the .NETurl==http://=http:///url cross-platform consideration, because it's really an emulation of Windows CLR support, and is always behind the current .NETurl==http://=http:///url curve. It's a hack, in other words, to get .NETurl==http://=http:///url code running on linix OS's. It's not something I would consider for a business or mission-critical development platform.

Yea, I have to write a 2-3 page paper on the differences of these. Its not for a class so I don't need sources and whatnot. Its just for a job so I can acclimate myself with their systems.

I mean what points should I cover and how indepth should I go. Dmorris, if you were writing this, how would you structure it?

Like, page 1 - Advantages and disadvantages of J2EE

page 2 - Advantages and disadvantages of .neturl==http://=http:///url

page 3 - contrast the 2?

or would you do a mix of that throughout