Java bruhaha

[Shedmasster]

What are the pitfalls of using Java?

The reason I ask is that I am currently trying to design a shop which uses a java based solution (the demo if the system that I want to use can be found at

http://www.uburst.com/uShop/demo/index.html)

I like the idea of the always viewable and updateable shopping cart so this seems perfect but I've been told that Java can be troublesome and may not even be supported by Microsft browsers anymore. Is this true? What are the implications of carrying on with implementing this system?

The design as I have it at the moment can be found at

http://www.shedfed.co.uk/chaytow/index.html.

Note that at the moment, only the beaver scout page and the sweatshirt link therein work (there is also an image missing to submit the order). Do you think that the Java shop solution is viable?

TIA.

 

[wushutwist]

All of the Java Browser issues can be completely avoided if you go strictly with a Server-Side Jave solution (Servlets/JSP).

I believe J2EE is the strongest Web Application Framework currently available and it is used extensively. It offers loads more relibility and scalebility then Windows DNA architecture. .NET may be the only real alternately and it is still largely vaporware.

Here is a pretty good article comparing both J2EE and .NET:

http://www.theserverside.com/resources/article.jsp?l=J2EE-vs-DOTNET

If I were you I would try to stay away from Applets and perform everything on the Server. The product that you are looking at may be very good but I think you could find a similar product that uses Servlets/JSP to achieve the same goal. Wushutwist