Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: buckworks
It was easy to install though - I even did it myself (which is saying something!)
not sure why pbreit feels this way. java and the MVC model allows for one to code an excellent and quite flexible shopping cart. not to mention the built in jvm secure functions are another advantage.
inaccessible? not sure what is meant by this.
granted java is not as easy to manipulate for non-java programmers, but that should be part of the decision making process.
If you're putting up a website, you're going to be best served using technologies that stay on your server, under your control. A Java applet or ActiveX object is running on the client's machine, is slower than dynamic HTML, and can generally be duplicated on the server side with minimal effort. The only advantage I can see to using applets/ActiveX is that they can be integrated into your site with fewer steps. To my mind, that's not enough of a bonus to justify this method.
As far as JSP/Servlet carts, I think you're not looking hard enough.
For instance, our company (why we can't name our products if they are relevant to the thread baffles me), has developed the leading mid-market ecommerce solution for the J2EE platform. It is written with Java using servlets and JSP. The benefits of which are open standards (no hardware restrictions as it will run on anything: Windows, Linux, Unix, Mac etc. and no Database restrictions as it will use Oracle, MS SQL, mySQL, DB2 etc.)
As for Java being slow, yes it has that notariety within client side applications, but when using web technologies such as JSP to deliver the data, there is no performance hindrance.
Java should be seriously considered as a ecommerce technology as it scales much better than proprietary languages.
Would You Ever Use A Java Applet Cart?
No way. even online banks that where about the only people are getting rid of this.
Basically you have to download the whole application from the server to the workstation and then run the software on your workstation. It might work, (Java: write once, debug everywhere) but why take the chances?
Sun itself very soon realized that for the broad market java appleets where a non-starter, so they introduced servlets and JSP to handle the work on the server.