I am trying to design a system wherein applets will be used to design the GUI and perform basic validations. The business logic resides in Servlets.
The front-end needs menus. Hence, I am not using HTML-servlets. Only the first servlet throws HTML with an embedded APPLET tag. With this APPLET tag I am fetching all the classes at the browser. This APPLET creates a main window(frame on top of the browser) from which other child frames will be created as and when we click on the menu items.
In these child windows I will be accepting user input, packaging them in a serializable object and sending it over to some other servlet which processes the info contained in the object. The servlet might update a DB table or send some other object back to the originator (child) window.
(Mind you, this servlet does NOT send any HTML tag. HTMLs are sent only by the first servlet).
My questions are:
1) Is this a good architecture. Can someone suggest something better. In fact, Sun's Java Web servers admin console uses a similar architecture.
2) If the child window need to send a serializable object to the servlet, can it do so directly. Or, will it have to ge through the main frame or the applet...
How does it do it? Does it just open a connection to the servlet and write to it as is normally done in simple applet-servlet communication?
3) Does any one know whether the source codes are available for the corresponding .class files available in jstadmin.zip with Sun's JavaWebServer2.0