Elements of Web Module Design
Since mid-2000, Java Servlet specs require containers to manage web apps as modules,
easily installed and hosted as a portable unit. Such modules are Lexikos specialties,
and we can create all the typical types and variations. Regardless of the particular
application, these core components are almost always involved;
Servlets, Java Server Pages, Custom Tags, Filters
Best practice generally makes the Servlet the module executive. Under the MVC design
pattern, it dispatches to all elements below, driving JSP "views" for output. A key
decision is output format: HTML or XML (mapped N ways using filters). Java Standard
Tag Library and custom tags offer powerful ways to divide coding and presentations.
Personalization and Security Options
Few web apps can omit these features, which are vital in most interactive designs.
They must be articulated early, as key parts of a site's global functionality, and
in practice often are the most difficult parts to get right.
Simpler Alternatives to EJBs
EJBs allow real time web access to a data base, but at large costs in complexity,
support needs, delays, etc. There are many other ways to manage persistent storage,
which often provide greater functionality at lower costs.
Messaging and E-Mail Options
These can greatly aid a module's functionality, and link it to other parts of
the enterprise in clean, simple ways. Ignore them, and you miss a great
chance to elegantly integrate a new module into your operations.
Templates, Tagsets, Beans, Packages
Module implementation uses these basic support aids, on which your staff
will spend 90% its time once a design exists. We may be able to offer
site-licensed versions which Lexikos customizes to your specs. This won't change
your core design, but it will help you optimize related coding plans.
|
