comparison of J2EE and .Net

  • Thread starter Thread starter Raheel
  • Start date Start date
R

Raheel

i h'd like to konw the list of things SUN J2EE could do
but .net can't, while things which .Net can do which J2EE
can't.

PLus

I also h'd lke to know how .net implementation of the pet
store is different from SUN (e.g. architecture like
3tiers, )security and how .net achieves security and
scalibility over J2EE.
 
Raheel said:
i h'd like to konw the list of things SUN J2EE could do
but .net can't, while things which .Net can do which J2EE
can't.
Click to expand...

Not sure that one can do something that the other can't.

PLus

I also h'd lke to know how .net implementation of the pet
store is different from SUN (e.g. architecture like
3tiers, )security and how .net achieves security and
scalibility over J2EE.
Click to expand...


You need to read up on the .NET Framework. I doubt anyone could express in
a reply to your post everything that you are asking.
 
I think the major difference is that .Net is Java but not with one language
but all you can possibly add.
Another difference is that Like Java, .Net app are complied to native the
first time but they are not trashed rather the next client would use the
native compiled copy.
The native copy is used day after day unless there is a change to the code.
if so the next client will get a freshly compiled copy.
Some JIT like hotstop for Java do run time optimisations which gets better
with each compile but i guess after a few good run the performance would
near .Net apps performance..
Plus you have great features like Web Controls and Asp.net which are pretty
event oriented for a web application. You have Remoting which is equivalent
of classic DCOM and ofcourse WebServices.

So its your choice.

Hermit Dave
 
Hermit Dave said:
I think the major difference is that .Net is Java but not with one language
but all you can possibly add.
Click to expand...

Actually there are many, many languages which have been targetted for
JVMs, although obviously Java is the most commonly used one.
Another difference is that Like Java, .Net app are complied to native the
first time but they are not trashed rather the next client would use the
native compiled copy.
Click to expand...

That's not true - the .NET JIT runs each time unless you ngen the
assembly first.
The native copy is used day after day unless there is a change to the code.
if so the next client will get a freshly compiled copy.
Some JIT like hotstop for Java do run time optimisations which gets better
with each compile but i guess after a few good run the performance would
near .Net apps performance..
Click to expand...

The fact that Hotspot compile more than once also allows it to make
optimisations which may turn out to be invalid later on: for instance,
virtual methods can be treated as final ones until they are overridden,
which can improve performance significantly.
Plus you have great features like Web Controls and Asp.net which are pretty
event oriented for a web application. You have Remoting which is equivalent
of classic DCOM and ofcourse WebServices.
Click to expand...

.... whereas in Java you'd use JSPs, RMI and still web services.
 
Jon Skeet said:
Actually there are many, many languages which have been targetted for
JVMs, although obviously Java is the most commonly used one.


That's not true - the .NET JIT runs each time unless you ngen the
assembly first.


The fact that Hotspot compile more than once also allows it to make
optimisations which may turn out to be invalid later on: for instance,
virtual methods can be treated as final ones until they are overridden,
which can improve performance significantly.


... whereas in Java you'd use JSPs, RMI and still web services.
Click to expand...

Maybe just add that .Net integrate all those technologies in a coherent,
comprehensive framework in a simple and intuitive way.

 
Yes,
I haven't looked into many languages tragetting JVM... possibly but it never
to the extent it has with .Net... maybe it was just 'cause microsoft wanted
to crush Java (Read Sun -after its issues)
Yes .Net code has to be n-compiled to take make it really fast.
As for JSP and RMIs and EJbs and WebServices i agree they are synonymous but
not extactly to what .Net offers. JSP is more synonymous to classic ASP than
ASP.NET. They are indeed compiled to Java classes and byte code but there
isnt a precise seperation of presentation layer from presentation logic. And
ofcourse Events, you dont have much flexibility in those terms.
RMI is synonymous to Remoting but i would say its stands with DCOM. Would
probably need some patch work. Dont know if Sun is doing anything on RMI in
its Sun One initiative.
EJBs stand somewhere between COM and .Net components but they do have a lot
of application server support. COM+ being the only applicaion server for COM
and now the .Net components
Plus this is just the software aspect of decision making. Dont forget your
hardware costs. Why on earth would anyone Java on Windows box (apart from
good dev environments), when they dont fail to curse microsoft for almost
everything. So if you have sufficient funds you will have to spend couple of
thousands on a solaris box. I wish people with lot of money could lend me
some instead.... my dual procs getting old and i would like replace it with
a AMD64(probably cost 1/10 the price of a solaris box unless you try it on
x86 arch.. but god have mercy on your soul - cause the driver support
sucks).
 
Yes .Net code has to be n-compiled to take make it really fast.
Click to expand...

No it doesn't. JIT compilation itself really doesn't take that long,
when seen in the context of the whole lifetime of the process.
As for JSP and RMIs and EJbs and WebServices i agree they are synonymous but
not extactly to what .Net offers. JSP is more synonymous to classic ASP than
ASP.NET. They are indeed compiled to Java classes and byte code but there
isnt a precise seperation of presentation layer from presentation logic.
Click to expand...

If you want to do things badly and mix business logic and presentation
logic, you can do so on either platform. I agree that the "code
behind" idea is a good one in ASP.NET though.
And ofcourse Events, you dont have much flexibility in those terms.
Click to expand...

It's certainly not event-driven in the way that ASP.NET is, but I'm not
sure whether or not that's actually an advantage. ASP.NET seems to be
trying to hide the real request-response nature of web-browsing by
making it all look like Windows forms. It's the kind of thing which is
great when it works, and a pain when it doesn't - I generally prefer to
have as little "magic" (like Javascript being generated automatically)
done for me as possible. (I don't use GUI wizards generally, for
instance.)
RMI is synonymous to Remoting but i would say its stands with DCOM. Would
probably need some patch work. Dont know if Sun is doing anything on RMI in
its Sun One initiative.
EJBs stand somewhere between COM and .Net components but they do have a lot
of application server support. COM+ being the only applicaion server for COM
and now the .Net components
Click to expand...

Yes - EJBs do seem to do an awful lot, but I don't know enough about
either them or COM+ to make a good comparison.
Plus this is just the software aspect of decision making. Dont forget your
hardware costs. Why on earth would anyone Java on Windows box (apart from
good dev environments), when they dont fail to curse microsoft for almost
everything. So if you have sufficient funds you will have to spend couple of
thousands on a solaris box. I wish people with lot of money could lend me
some instead.... my dual procs getting old and i would like replace it with
a AMD64(probably cost 1/10 the price of a solaris box unless you try it on
x86 arch.. but god have mercy on your soul - cause the driver support
sucks).
Click to expand...

I don't see anything wrong with using Java on Windows, to be honest.
 
Back
Top