JSP vs Applet-Servlet vs Application
I am trying to decide whether to use an Applet-Servlet configuration for an web-based application I am developing. Ordinarily I develop using Cold Fusion (similar to ASP for those that don't know). However, one element that is required in the form I am currently developing is a malleable tree structure. Basically, this structure allows the user to create a tree of topics for the course lesson they are currently working on. This tree would catch keyboard actions and process them accordingly. e.g. if the user clicks the "Enter" button a new node is created directly beneath the currently selected node. if the user clicks the "Tab" button the node is moved to the right. etc... I could still use Cold Fusion with this since it has a tree structure, but the form would have to be submitted each time a node is addded/deleted and we're really looking to minimize page loads.
Since all the data for the lessons is stored in a SQL Server database, I was considering using an Applet-Servlet configuration for this, where the Applet was the GUI and sent messages to the Servlet to do the database work. However, I've been reading about some really nasty problems using JApplets in browsers (installing Java Plug-In, etc...).
So while I still favor this option, I've been looking at other possibilities. I've been reading some about JSP, but am not sure it would be able to do that tree structure I require. I've also looked at doing this as a Java application, but then I understand I'd have to install a DSN on everyone's computer that wishes to use the application. Since this application would be distributed to lots of different people in our intranet, this is not an option.
So my questions to you is, do you think I should just stick with the Applet-Servlet configuration or could one of the other 2 options (or some option I haven't considered yet) work better? Any input is very much appreciated!
[1945 byte] By [
MHoeppner] at [2007-9-26 2:08:42]
Hi, just a couple of suggestions:
> I am trying to decide whether to use an Applet-Servlet
> configuration for an web-based application I am
> developing. Ordinarily I develop using Cold Fusion
> (similar to ASP for those that don't know). However,
> one element that is required in the form I am
> currently developing is a malleable tree structure.
> Basically, this structure allows the user to create a
> tree of topics for the course lesson they are
> currently working on. This tree would catch keyboard
> actions and process them accordingly. e.g. if the
> user clicks the "Enter" button a new node is created
> directly beneath the currently selected node. if the
> user clicks the "Tab" button the node is moved to the
> right. etc... I could still use Cold Fusion with
> this since it has a tree structure, but the form
> would have to be submitted each time a node is
> addded/deleted and we're really looking to minimize
> page loads.
>
> Since all the data for the lessons is stored in a SQL
> Server database, I was considering using an
> Applet-Servlet configuration for this, where the
> Applet was the GUI and sent messages to the Servlet to
> do the database work. However, I've been reading
> about some really nasty problems using JApplets in
> browsers (installing Java Plug-In, etc...).
Do you really need a JApplet? if you develop the whole applet within awt you should be quite ok without plugins. (at least ns4, ns6, ie4, ie5)
>
> So while I still favor this option, I've been looking
> at other possibilities. I've been reading some about
> JSP, but am not sure it would be able to do that tree
> structure I require. I've also looked at doing this
> as a Java application, but then I understand I'd have
> to install a DSN on everyone's computer that wishes to
> use the application. Since this application would be
> distributed to lots of different people in our
> intranet, this is not an option.
>
> So my questions to you is, do you think I should just
> stick with the Applet-Servlet configuration or could
> one of the other 2 options (or some option I haven't
> considered yet) work better? Any input is very much
> appreciated!
ok as you can see the only input i had was the serv-app one. i really think this is the option for you. when you develop the applet just check that you never use classes added after jdk1.1 and you should be quite ok without plugins.
both awt and net are "since jdk1.0" so using these packages isn't an issue for you.
good luck
-Pr
> Do you really need a JApplet? if you develop the whole
> applet within awt you should be quite ok without
> plugins. (at least ns4, ns6, ie4, ie5)
...but this would mean he can't use a JTree to create his tree. Using a JTree would probably save a *lot* of work!
I'd use a Swing application front-end if possible/feasible. You might also look at using Java Web Start to deploy it to everyone on your intranet and to keep them updated with new versions etc.
If it must be browser based (IP problems?), then one other suggestion is to try WebCream, a product marketed by Cream Tec:
http://www.creamtec.com/webcream
This allows you to run a Swing app on your server and it converts the GUI to HTML/DHTML and sends it to the client - so the client gets something that looks similar to your Swing GUI, but made from DHTML (HTML+JavaScript).
I've never tried WebCream, but I'd be interested to hear from someone who has.
