L. Spasovski responds:
>>That's the nice thing about Enhydra, Tomcat etc, it can run on both
whereas
>>ASP can only run on Windows for free and at a cost on other machines.
That
>>gives one some flexibility if needed.
>Keyword : if needed. But looks that nobody will needed to switch everyday
>between systems. That's marketing tricks from many internet companies and
>consultants when they are talking to companies and use "Maybe you will NEED
>to switch systems". When you establish your IT infrastructure next changes
>are after many many years. Nobody is switching systems on yearly or monthly
>basis.

I may not have been clear.  I'm not suggesting that one would want to switch
systems every month, but I like to know that if a company goes out of
business or gets split up by the Justice Department, that I have some
options.  That's all.


>>EJB will offer the same capabilities of .NET most likely.
>Again keywords - most likely.

I say most likely because it seems there are very few people who know what
.NET is.  See
http://www.computerworld.com/cwi/story/0,1199,NAV47_STO60254,00.html.

>EJB is not even close to .NET techologies.

How do you know?  Both standards are still evolving.

>Building WEB application with .NET is more like building regular
>application. Code behind the web pages is completly separate and is event
>driven.

That's exactly how it works with Enhydra's XMLC.

>How ENHYDRA support EJB's? How about all J2EE part?

According to their web page: yes, yes. See:
http://enterprise.enhydra.org/project/aboutProject/index.html

>The big problem with JAVA, JAVA is proprietary language. Before couple
years
>many people were complaining they don't want proprietery things. But
>reallity is different JAVA is proprietary language. IT's not standard.
>One good thing about .NET is that by September or October will be promote
in
>STANDARD by ECMA (looks that initailly will be oround 200 classes included
>in that standard. Microsoft submit 700 but ECMA cannot standardize that
many
>in this period of time). Having standard that are not anymore controled by
>only ONE COMPANY , allow many other to start using and develop their own
>compilers and make available on many platforms, without paying for licence.

HP has its own clean-room version of Java (Chai, I believe) and IBM has the
Jikes Java compiler and there are other Java assemblers that allow one to
create class files without the Sun JDK.  While I do not like the grip that
Sun has on Java, I would still have to consider Java more open than .NET at
this point in time.  Java was in ECMA's sights right to the last minute, so
I'll wait and see if it really does happen with .NET too.

>I'm not microsoft fan neither any other fan. I'm just trying to use
whatever
>is available with minimal cost.

I'm not trying to start a religious war and I agree with you here.  I'll use
whatever tool solves my problem with the lowest total cost.  I also want to
protect my investments in software development.  What has happened to all
who bought into Windows DNA/COM/DCOM...?  Does .NET replace that?  Many
companies are into Java.  If Sun went out of business tomorrow, there would
be someone to carry on.  If Microsoft were split up...well I'm not no sure
there would be many to save .NET at this point.

Kind regards,

Mark Wonsil

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *