best practices?

["Joseph B. Ottinger" <jo...@suninternet.com>]

For my J2EE example application, rather than continue poorly-planned
development without any knowledge whatsoever, I designed a very simple
entity bean, and implemented a set of pages to modify, add, and query the
backend for the entities. As this is the first "road test" for J2EE
for me, more or less, I'm not really sure if what I'm doing constitutes
any sort of best practices... but I've just not seen any real examples I'm
happy with yet.

Where do the lists come in? Well, I'm inviting review, and providing full
frontend source code (backend source code can be arranged, too, it's just
less important than the front end part, and slightly more proprietary as
well, as some of the configuration files are app-server specific.)

The url is http://cupid.suninternet.com/phonelist/fates

Feel free to mangle anything there. The only thing I know of that's broken
is that if you add an entry with a key that already exists, an exception
will be thrown; I plan on adding an errorpage soon to handle that. This
also shows the use of my form taglibrary, as well as orion's ejb tag
library.

The design goals were to have as few scriptlets as possible in the user
interface pages. I used JSP to do what servlets would be better at (the
actual update pages) because I'm lazy and didn't feel like writing an
actual servlet (and deployment here is easier, as well.) Feel free to
point out anything you'd like about these pages; my goal is to have
something available that I can look at and say "this is the proper way of
doing this" without worrying that I'm missing something critical.

-----------------------------------------------------------
Joseph B. Ottinger               joeo@cupid.suninternet.com
http://cupid.suninternet.com/~joeo      HOMES.COM Developer