Groups > comp.lang.java.programmer > #39657

Re: What's the deal with JSP?

Path	csiph.com!aioe.org!5Avcpu9drOe6MAssky6/+Q.user.gioia.aioe.org.POSTED!not-for-mail
From	Arne Vajhøj <arne@vajhoej.dk>
Newsgroups	comp.lang.java.programmer
Subject	Re: What's the deal with JSP?
Date	Tue, 29 Dec 2020 22:43:45 -0500
Organization	Aioe.org NNTP Server
Lines	43
Message-ID	<rsgt1f$1gtk$1@gioia.aioe.org> (permalink)
References	<3fb97b37-b0e7-48a3-a2b3-c4d1a828d6dbn@googlegroups.com> <rsftmh$8j4$1@gioia.aioe.org> <9d058e34-6f36-4322-a639-67de2b842012n@googlegroups.com>
NNTP-Posting-Host	5Avcpu9drOe6MAssky6/+Q.user.gioia.aioe.org
Mime-Version	1.0
Content-Type	text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding	7bit
X-Complaints-To	abuse@aioe.org
User-Agent	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
Content-Language	en-US
X-Notice	Filtered by postfilter v. 0.9.2
Xref	csiph.com comp.lang.java.programmer:39657

Show key headers only | View raw

On 12/29/2020 4:59 PM, e.d.pro...@gmail.com wrote:
>> A JSP page should consist of either a mix of markup and Java or
>> preferably only markup. If it was all Java then you should use
>> a servlet instead. So I think it makes sense for Eclipse to color
>> code it as HTML and not as Java.
>>
> It looked confusing with the default being html as I saw a class like myjsp.jsp got converted when it compiled to generate something like a myjsp_jsp.java.

 From an application perspective you should just look at
the JSP and what it does - how it does it should not
matter unless you are developing a web container. (*)

But yes typical the .jsp get converted into a .java that get compiled
into a .class that get loaded and JIT compiled to native code by the
JVM.

*) Actually looking at the generated .java can occasionally be useful
for troubleshooting certain compile errors.

>> <% %> are indeed considered primitive / old fashioned / bad style.
>> There are several techniques that can be used to avoid that
>> mix and get more clean code. Most important should be
>> JSTL and bean classes.
>>
> We have a lot of <% %> like the jsp files were written by a Java programmer who just wanted to make the entire jsp files into Java code with the html tags just stuck in between.
> <% if (condition) { %>
>     <tag>value</tag>
> <% } %>

It is bad style.

It was also common style 20 years ago.

:-)

> I did see the JSTL looks cleaner, though converting everything will take awhile. Trying to sort out what goes in front end, back end if this should be any sort of MVC since it's currently html, jsp, java, javascript all in one file.  I did see how to make a servlet, or tag files, to separate things out.  Just trying to clear up what should go where.

Some best practices, JSTL etc. improved JSP a lot in the early 00'es.

Of course with JSF 2.0 in 2009 and facelets becoming default view
technology, then JSP was no longer "it".

Arne

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

What's the deal with JSP? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2020-12-29 07:27 -0800
  Re: What's the deal with JSP? Arne Vajhøj <arne@vajhoej.dk> - 2020-12-29 13:48 -0500
    Re: What's the deal with JSP? "e.d.pro...@gmail.com" <e.d.programmer@gmail.com> - 2020-12-29 13:59 -0800
      Re: What's the deal with JSP? Arne Vajhøj <arne@vajhoej.dk> - 2020-12-29 22:43 -0500

csiph-web