Hi Joel,
this time, I entirely agree with you... :-) That's why I'll take the
opportunity to call your attention to an important issue. Please let
us know what you think about this.
The Application Programming Model document that is bundled with Sun's
J2EE RI openly recommends the use of JavaScript along with HTML as a
means to enhance the GUI. I guess the document insists on this point
because, at the same time, the use of applets as clients (which can
neatly implement any complex GUI, of course) is openly discouraged.
Just to give you some examples:
"5.3 Web Clients
... In these clients, the user interface presented to the end user is
generated on the server side by the Web tier and communicated via HTML
or DHTML. Additionally, applets and *JavaScript* may be used to enhance
the browsing interface."
"5.3.3.1 Web Browser
The Web browser is the simplest J2EE client. It serves to render HTML
content delivered by the Web tier. With more and more browsers supporting
*JavaScript* and DHTML, powerful user interfaces can be created using
just the Web browser."
"5.4.1.1 Recommendations
... Web clients should be used when possible. With DHTML and *JavaScript*,
the browser can support a reasonably powerful and fast user interface.
Additionally applets can enhance it even further."
As you see, applets are mentioned in those excerpts only as a means to
enhance the GUI (in a way that, as you know, usually overlaps with
JavaScript).
Don't you think this is inconsistent with the whole J2EE concept? It's just
too easy to embed business logic in a Web page when you use a JHTML/JSP/
JavaScript/ASP approach... Such an approach should not be recommended,
in my opinion, by the designers of J2EE, who are also the authors of the
APM document.
Am I that wrong?
Best regards,
Cris
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
