> 1) How do I choose between using JHTML and JSP. They seem to be overlapping
> 2) Which one of these will be supported by iPlanet and ND 5.0.2 ?
> 3) What is the advantage of JSP/JHTML over traditional ND templates.
Hi,
JHTML and JSP and Java Servlets do indeed overlap.
JHTML is basic, JSP is medium, and Servlets are advanced.
In my experience, I would choose JHTML if I were developing a simple
project with developers who understand HTML and little else. JHTML
is like CFML (ColdFusion) and ASP, and will be fine for these kinds
of projects.
JSP (Java Server Pages) is a more sophisticated way to build dynamic HTML
pages. You embed Java code into your pages, and there are easy ways to get
and set variables, as well as easy ways to write full-fledged Java code.
In my experience, JSP is fine for quick-and-dirty projects for developers
who are comfortable writing real Java and/or who have good Java beans.
When a JSP page is loaded, it is automatically compiled into a servlet;
so at run time, there is absolutely no difference between the two.
The difference is that JSPs are quick and easy to write, whereas
servlets require you to use the javax.servlet package and truly
compile your code.
Like most technologies, there is a tradeoff between easy quick approaches
and advanced profession approaches. I would absolutely use servlets for
any kind of important project, and I would probably use JHTML for easy
things like prototyping. I am not a big fan of JSP because I think it is
overly complex for easy things, and overly loose for complex things.
So in general, I recommend servlets.
ND5 already supports servlets for development, and the new ND 5.02
supports servlets for deployment as well. IAS6 will support these too.
The advantage of JSP over ND templates is that JSP is a standard
technologies, and will allow embedding of arbitrary code. There
are also third-party editors that can edit well-written JSP pages,
especially if you use the XML-style JSP syntax (not <%...%> markup)
In general, I recommend separating the display (the HTML/XML) from the
application logic (Java/servlets). The separation tends to improve
flexibility and reusability, and is also easier for development teams that
combine artists and programmers. I think mixing HTML and code, in general,
leads to problems down the line-- so I try to minimize my use of templates
like ND.spg, JSP, ASP, etc.
What do other people here think?
Cheers,
Joel
home: [EMAIL PROTECTED]
work: [EMAIL PROTECTED]
_________________________________________________________________________
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]
