Best Option

[pratap maha]

Hi -
I am in a dilema if I have to use a JApplet to build a rich GUI on the clinet side. I am only having Apahe HTTP Server on a AIX box. Do I have any other options ?. Thanks,

Maha

[Gregg Bolinger]

I am not sure what your question means. To me you are saying you *have* to write an applet, but you want other options?? If you have to write an applet, it seems to me that your only option is an applet. Does this have anything to do with JavaServer Faces? This forum is for JSF. If it is not, let's figure out what you want and get you to the right place where you can get some good answers.

[H Wilson]

Originally posted by pratap maha:
Hi -
I am in a dilema if I have to use a JApplet to build a rich GUI on the clinet side.

Are you saying, "Do I have to use an applet in order to get a rich GUI on the client side?" If you want something significantly richer than what html provides, I think the answer may be "yes."

[pratap maha]

Hi -

Sorry for not being clear. I am looking for some other technologies than JApplet with the only resource avaliable HTTP Server to render a rich GUI on client side. Thx,

Maha

[Gregg Bolinger]

There are a lot of options at your disposal. The problem is web pages can only be so *rich* so I would recommend getting some requirements for the project and then that will help you better determine what technology you will need to go with. If you want to post some of those requirements here we will be glad to help.

JavaServer Faces and Tapestry are probably the closest *rich* solutions that are also commonly used. They both are reminisce of a Swing like API in that they are based on using components to build web pages and a sort of backing bean to handle the components model. You can get a lot of things done quickly with these 2 technologies. However, they won't do anything more than Struts, WebWork, or plain old JSP/Servlets. Frameworks just help speed up development. In the end it's all HTML and Javascript.