How can I avoid Java code in JSP files using JSP 2

Question

I m new to Java EE and I know that something like the following three lines  lt    x 1   gt   lt    request getParameter  quot name quot     gt   lt    counter      gt   is an old school way of coding and in JSP version 2 there exists a method to avoid Java code in JSP files  What are the alternative JSP 2 lines  and what is this technique called

User · Answer

In the MVC architectural pattern  JSPs represent the view layer  Embedding Java code in JSPs is considered a bad practice  You can use JSTL  freeMarker  and velocity with JSP as a  quot template engine quot   The data provider to those tags depends on frameworks that you are dealing with  Struts 2 and WebWork as an implementation for the MVC pattern uses OGNL  quot very interesting technique to expose Beans properties to JSP quot

User · Answer

A lot of the answers here go the  quot use a framework quot  route  There s zero wrong with that  However I don t think it really answers your question  because frameworks may or may not use JSPs  nor are they designed in any way with removing java use in JSPs as a primary goal   The only good answer to your question  quot how do I avoid using Java in a JSP quot  is  you can t   That s what JSPs are for - using Java to render HTML with dynamic data logic  The follow up question might be  how much java should I use in my JSPs  Before we answer that question  you should also ponder   quot do I need to use JSPs to build web content using Java  quot  The answer to that last one is  no  There are many alternatives to JSPs for developing web facing applications using Java  Struts for example does not force you to use JSPs - don t get me wrong  you can use them and many implementations do  but you don t absolutely have to  Struts doesn t even force you to use any HTML  A JSP doesn t either  but let s be honest  a JSP producing no HTML is kinda weird  Servlets  famously  allow you to serve any kind of content you like over HTTP dynamically  They are the primary tech behind pretty much everything java web - JSPs are just HTML templates for servlets  really   So the answer to how much java you should put in a JSP is   quot as little as possible quot   I of course have java in my JSPs  but it consists exclusively of tag library definitions  session and client variables  and beans encapsulating server side objects  The  lt    gt  tags in my HTML are almost exclusively property calls or variable expressions  Rare exceptions include ultra-specific calculations pertaining to a single page and unlikely to ever be reused  bugfixes stemming from page-specific issues only applying to one page  last minute concatenations and arithmetic stemming from unusual requirements limited in scope to a single page  and other similar cases  In a code set of 1 5 million lines  3000 JSPs and 5000 classes  there are maybe 100 instances of such unique snippets  It would have been quite possible to make these changes in classes or tag library definitions  but it would have been inordinately complex due to the specificity of each case  taken longer to write and debug  and taken more time as a result to get to my users  It s a judgement call  But make no mistake  you cannot write JSPs of any meaning with  quot no java quot  nor would you want to  The capability is there for a reason

User · Answer

If you simply want to avoid the drawbacks of Java coding in JSP you can do so even with scriplets  Just follow some discipline to have minimal Java in JSP and almost no calculation and logic in the JSP page   lt    page contentType  quot text html charset UTF-8 quot  language  quot java quot    gt   lt      Instantiate a JSP controller MyController clr   new MyController request  response       Process action  if any clr process request       Process page forwarding  if necessary     Do all variable assignment here String showMe   clr getShowMe     gt    lt html gt       lt head gt       lt  head gt       lt body gt           lt form name  quot frm1 quot  gt               lt p gt  lt    showMe   gt               lt p gt  lt   for String str   clr listOfStrings        gt               lt p gt  lt    str   gt  lt       gt                  And so on             lt  form gt       lt  body gt   lt  html gt

User · Answer

As a Safeguard  Disable Scriptlets For Good  As another question is discussing  you can and always should disable scriptlets in your web xml web application descriptor   I would always do that in order to prevent any developer adding scriptlets  especially in bigger companies where you will lose overview sooner or later  The web xml settings look like this    lt jsp-config gt     lt jsp-property-group gt       lt url-pattern gt   jsp lt  url-pattern gt        lt scripting-invalid gt true lt  scripting-invalid gt     lt  jsp-property-group gt   lt  jsp-config gt

User · Answer

Use JSTL tag libraries in JSP  That will work perfectly

User · Answer

You can use JSTL tags together with EL expressions to avoid intermixing Java and HTML code    lt    page contentType  text html charset UTF-8  language  java    gt   lt    taglib uri  http   java sun com jsp jstl core  prefix  c    gt   lt    taglib uri  http   java sun com jsp jstl fmt  prefix  fmt    gt   lt html gt       lt head gt       lt  head gt       lt body gt            lt c out value    x   1     gt           lt c out value    param name     gt             and so on       lt  body gt   lt  html gt

User · Answer

Learn to customize and write your own tags using JSTL Note that EL is EviL  runtime exceptions and refactoring   Wicket may be evil too  performance and toilsome for small applications or simple view tier   Example from java2s This must be added to the web application s web xml  lt taglib gt       lt taglib-uri gt  java2s lt  taglib-uri gt       lt taglib-location gt  WEB-INF java2s tld lt  taglib-location gt   lt  taglib gt   Create file java2s tld in the  WEB-INF   lt  DOCTYPE taglib   PUBLIC  quot -  Sun Microsystems  Inc   DTD JSP Tag Library 1 2  EN quot      quot http   java sun com dtd web-jsptaglibrary 1 2 dtd quot  gt    lt  -- A tab library descriptor -- gt   lt taglib xmlns  quot http   java sun com JSP TagLibraryDescriptor quot  gt       lt tlib-version gt 1 0 lt  tlib-version gt       lt jsp-version gt 1 2 lt  jsp-version gt       lt short-name gt Java2s Simple Tags lt  short-name gt        lt  -- This tag manipulates its body content by converting it to upper case     -- gt       lt tag gt           lt name gt bodyContentTag lt  name gt           lt tag-class gt com java2s BodyContentTag lt  tag-class gt           lt body-content gt JSP lt  body-content gt           lt attribute gt             lt name gt howMany lt  name gt           lt  attribute gt       lt  tag gt   lt  taglib gt   Compile the following code into WEB-INF classes com java2s package com java2s   import java io IOException  import javax servlet jsp JspWriter  import javax servlet jsp tagext BodyContent  import javax servlet jsp tagext BodyTagSupport   public class BodyContentTag extends BodyTagSupport      private int iterations  howMany       public void setHowMany int i           this howMany   i             public void setBodyContent BodyContent bc           super setBodyContent bc           System out println  quot BodyContent     quot    bc getString      quot   quot               public int doAfterBody            try              BodyContent bodyContent   super getBodyContent                String bodyString    bodyContent getString                JspWriter out   bodyContent getEnclosingWriter                 if   iterations   2    0                   out print bodyString toLowerCase                 else                 out print bodyString toUpperCase                  iterations                bodyContent clear       empty buffer for next evaluation                   catch  IOException e                System out println  quot Error in BodyContentTag doAfterBody   quot    e getMessage                 e printStackTrace                 End of catch          int retValue   SKIP BODY           if   iterations  lt  howMany               retValue   EVAL BODY AGAIN           return retValue           Start the server and load the bodyContent jsp file in the browser   lt    taglib uri  quot  java2s quot  prefix  quot java2s quot    gt   lt html gt       lt head gt           lt title gt A custom tag  body content lt  title gt       lt  head gt       lt body gt          This page uses a custom tag manipulates its body content Here is its output           lt ol gt               lt java2s bodyContentTag howMany  quot 3 quot  gt               lt li gt java2s com lt  li gt               lt  java2s bodyContentTag gt           lt  ol gt       lt  body gt   lt  html gt

User · Answer

Make your values and parameters inside your servlet classes Fetch those values and parameters within your JSP using JSTL Taglib      The good thing about this approach is that your code is also HTML like   code

User · Answer

JSP 2 0 has a feature called  quot Tag Files quot   and you can write tags without external Java code and tld  You need to create a  tag file and put it in WEB-INF tags  You can even create a directory structure to package your tags  For example   WEB-INF tags html label tag   lt   tag description  quot Rensders a label with required css class quot  pageEncoding  quot UTF-8 quot   gt   lt   attribute name  quot name quot  required  quot true quot  description  quot The label quot   gt    lt label class  quot control-label control-default quot   id  quot   name Label quot  gt   name  lt  label gt   Use it like  lt    taglib prefix  quot h quot  tagdir  quot  WEB-INF tags html quot   gt   lt h label  name  quot customer name quot    gt   Also  you can read the tag body easily   WEB-INF tags html bold tag  lt   tag description  quot Bold tag quot  pageEncoding  quot UTF-8 quot   gt   lt b gt     lt jsp doBody  gt   lt  b gt   Use it   lt    taglib prefix  quot h quot  tagdir  quot  WEB-INF tags bold quot   gt   lt h bold gt Make me bold lt  h bold gt   The samples are very simple  but you can do lots of complicated tasks here  Please consider you can use other tags  for example  JSTL which has controlling tags like if forEcah chosen text manipulation like format contains uppercase or even SQL tags select update   pass all kind parameters  for example Hashmap  access session  request      in your tag file too  Tag File are so easy developed as you did not need to restart the server when changing them  like JSP files  This makes them easy for development  Even if you use a framework like Struts 2  which have lots of good tags  you may find that having your own tags can reduce your code a lot  You can pass your tag parameters to struts and this way customize your framework tag  You can use tags not only to avoid Java  but also minimize your HTML codes  I myself try to review HTML code and build tags a lot as soon as I see code duplicates start in my pages   Even if you end up using Java in your JSP code  which I hope not  you can encapsulate that code in a tag

User · Answer

As many answers says  use JSTL or create your own custom tags  Here is a good explanation about creating custom tags

User · Answer

The use of scriptlets  those  lt     gt  things  in JSP is indeed highly discouraged since the birth of taglibs  like JSTL  and EL  Expression Language  those     things  way back in 2001   The major disadvantages of scriptlets are    Reusability  you can t reuse scriptlets  Replaceability  you can t make scriptlets abstract  OO-ability  you can t make use of inheritance composition  Debuggability  if scriptlet throws an exception halfway  all you get is a blank page  Testability  scriptlets are not unit-testable  Maintainability  per saldo more time is needed to maintain mingled cluttered duplicated code logic    Sun Oracle itself also recommends in the JSP coding conventions to avoid use of scriptlets whenever the same functionality is possible by  tag  classes  Here are several cites of relevance      From JSP 1 2 Specification  it is highly recommended that the JSP Standard Tag Library   JSTL  be used in your web application to help reduce the need for JSP scriptlets in your pages  Pages that use JSTL are  in general  easier to read and maintain                 Where possible  avoid JSP scriptlets whenever tag libraries provide equivalent functionality  This makes pages easier to read and maintain  helps to separate business logic from presentation logic  and will make your pages easier to evolve into JSP 2 0-style pages  JSP 2 0 Specification supports but de-emphasizes the use of scriptlets                 In the spirit of adopting the model-view-controller  MVC  design pattern to reduce coupling between the presentation tier from the business logic  JSP scriptlets should not be used for writing business logic  Rather  JSP scriptlets are used if necessary to transform data  also called  value objects   returned from processing the client s requests into a proper client-ready format  Even then  this would be better done with a front controller servlet or a custom tag      How to replace scriptlets entirely depends on the sole purpose of the code logic  More than often this code is to be placed in a fullworthy Java class    If you want to invoke the same Java code on every request  less-or-more regardless of the requested page  e g  checking if a user is logged in  then implement a filter and write code accordingly in doFilter   method  E g    public void doFilter ServletRequest request  ServletResponse response  FilterChain chain  throws ServletException  IOException       if    HttpServletRequest  request  getSession   getAttribute  user      null              HttpServletResponse  response  sendRedirect  login       Not logged in  redirect to login page        else           chain doFilter request  response      Logged in  just continue request            When mapped on an appropriate  lt url-pattern gt  covering the JSP pages of interest  then you don t need to copypaste the same piece of code overall JSP pages    If you want to invoke some Java code to preprocess a request  e g  preloading some list from a database to display in some table  if necessary based on some query parameters  then implement a servlet and write code accordingly in doGet   method  E g    protected void doGet HttpServletRequest request  HttpServletResponse response  throws ServletException  IOException       try           List lt Product gt  products   productService list       Obtain all products          request setAttribute  products   products      Store products in request scope          request getRequestDispatcher   WEB-INF products jsp   forward request  response      Forward to JSP page to display them in a HTML table        catch  SQLException e            throw new ServletException  Retrieving products failed    e             This way dealing with exceptions is easier  The DB is not accessed in the midst of JSP rendering  but far before the JSP is been displayed  You still have the possibility to change the response whenever the DB access throws an exception  In the above example  the default error 500 page will be displayed which you can anyway customize by an  lt error-page gt  in web xml    If you want to invoke some Java code to postprocess a request  e g  processing a form submit  then implement a servlet and write code accordingly in doPost   method  E g    protected void doPost HttpServletRequest request  HttpServletResponse response  throws ServletException  IOException       String username   request getParameter  username        String password   request getParameter  password        User user   userService find username  password        if  user    null            request getSession   setAttribute  user   user      Login user          response sendRedirect  home       Redirect to home page        else           request setAttribute  message    Unknown username password  Please retry        Store error message in request scope          request getRequestDispatcher   WEB-INF login jsp   forward request  response      Forward to JSP page to redisplay login form with error            This way dealing with different result page destinations is easier  redisplaying the form with validation errors in case of an error  in this particular example you can redisplay it using   message  in EL   or just taking to the desired target page in case of success    If you want to invoke some Java code to control the execution plan and or the destination of the request and the response  then implement a servlet according to the MVC s Front Controller Pattern  E g    protected void service HttpServletRequest request  HttpServletResponse response  throws ServletException  IOException       try           Action action   ActionFactory getAction request           String view   action execute request  response            if  view equals request getPathInfo   substring 1                 request getRequestDispatcher   WEB-INF     view     jsp   forward request  response             else               response sendRedirect view                   catch  Exception e            throw new ServletException  Executing action failed    e             Or just adopt an MVC framework like JSF  Spring MVC  Wicket  etc so that you end up with just a JSP Facelets page and a JavaBean class without the need for a custom servlet    If you want to invoke some Java code to control the flow inside a JSP page  then you need to grab an  existing  flow control taglib like JSTL core  E g  displaying List lt Product gt  in a table    lt    taglib uri  http   java sun com jsp jstl core  prefix  c    gt       lt table gt       lt c forEach items    products   var  product  gt           lt tr gt               lt td gt   product name  lt  td gt               lt td gt   product description  lt  td gt               lt td gt   product price  lt  td gt           lt  tr gt       lt  c forEach gt   lt  table gt    With XML-style tags which fit nicely among all that HTML  the code is better readable  and thus better maintainable  than a bunch of scriptlets with various opening and closing braces   Where the heck does this closing brace belong to     An easy aid is to configure your web application to throw an exception whenever scriptlets are still been used by adding the following piece to web xml    lt jsp-config gt       lt jsp-property-group gt           lt url-pattern gt   jsp lt  url-pattern gt           lt scripting-invalid gt true lt  scripting-invalid gt       lt  jsp-property-group gt   lt  jsp-config gt    In Facelets  the successor of JSP  which is part of the Java EE provided MVC framework JSF  it is already not possible to use scriptlets  This way you re automatically forced to do things  the right way     If you want to invoke some Java code to access and display  backend  data inside a JSP page  then you need to use EL  Expression Language   those     things  E g  redisplaying submitted input values    lt input type  text  name  foo  value    param foo     gt    The   param foo  displays the outcome of request getParameter  foo      If you want to invoke some utility Java code directly in the JSP page  typically public static methods   then you need to define them as EL functions  There s a standard functions taglib in JSTL  but you can also easily create functions yourself  Here s an example how JSTL fn escapeXml is useful to prevent XSS attacks    lt    taglib uri  http   java sun com jsp jstl functions  prefix  fn    gt       lt input type  text  name  foo  value    fn escapeXml param foo      gt    Note that the XSS sensitivity is in no way specifically related to Java JSP JSTL EL whatever  this problem needs to be taken into account in every web application you develop  The problem of scriptlets is that it provides no way of builtin preventions  at least not using the standard Java API  JSP s successor Facelets has already implicit HTML escaping  so you don t need to worry about XSS holes in Facelets    See also    What s the difference between JSP  Servlet and JSF  How does Servlet  ServletContext  HttpSession and HttpServletRequest Response work  Basic MVC example with JSP  Servlet and JDBC Design patterns in Java web applications Hidden features of JSP Servlet

User · Answer

How can I avoid Java code in JSP files  You can use tab library tags like JSTL in addition to Expression Language  EL   But EL does not work well with JSP  So it s is probably better to drop JSP completely and use Facelets  Facelets is the first non JSP page declaration language designed for JSF  Java Server Faces  which provided a simpler and more powerful programming model to JSF developers as compare to JSP  It resolves different issues occurs in JSP for web applications development   Source

User · Answer

Experience has shown that JSP s have some shortcomings  one of them being hard to avoid mixing markup with actual code   If you can  then consider using a specialized technology for what you need to do   In Java EE 6 there is JSF 2 0  which provides a lot of nice features including gluing Java beans together with JSF pages through the   bean method argument   approach

User · Answer

Nothing of that is used anymore  my friend  My advice is to decouple the view  CSS  HTML  JavaScript  etc   from the server  In my case  I do my systems handling the view with Angular and any data needed is brought from the server using REST services  Believe me  this will change the way you design

User · Answer

Using Scriptlets is a very old way and not recommended  If you want directly output something in your JSP pages  just use Expression Language  EL   along with JSTL  There are also other options  such as using a templating engine such as Velocity  Freemarker  Thymeleaf  etc  But using plain JSP with EL and JSTL serves my purpose most of the time and it also seems the simplest for a beginner  Also  take note that it is not a best practice to do business logic in the view layer  You should perform your business logic in the service layer  and pass the output result to your views through a controller

User · Answer

A neat idea from the Python world is Template attribute languages  TAL was introduced by Zope  therefore a k a   quot Zope Page Templates quot   ZPT  and is a standard  with implementations in PHP  XSLT and Java as well  I have used the Python Zope and PHP incarnations   In this class of templating languages  one of the above examples could look like this   lt table gt       lt tr tal repeat  quot product products quot  gt           lt td tal content  quot product name quot  gt Example product lt  td gt           lt td tal content  quot product description quot  gt A nice description lt  td gt           lt td tal content  quot product price quot  gt 1 23 lt  td gt       lt  tr gt   lt  table gt   The code looks like ordinary HTML  or XHTML  plus some special attributes in an XML namespace  it can be viewed with a browser and safely be tweaked by a designer  There is support for macros and for internationalisation and localisation as well   lt h1 i18n translate  quot  quot  gt Our special offers lt  h1 gt   lt table gt       lt tr tal repeat  quot product products quot  gt           lt td tal content  quot product name quot              i18n translate  quot  quot  gt Example product lt  td gt           lt td tal content  quot product description quot              i18n translate  quot  quot  gt A nice description lt  td gt           lt td tal content  quot product price quot  gt 1 23 lt  td gt       lt  tr gt   lt  table gt   If translations of the content are available  they are used  I don t know very much about the Java implementation  though

User · Answer

You raised a good question and although you got good answers  I would suggest that you get rid of JSP  It is outdated technology which eventually will die  Use a modern approach  like template engines  You will have very clear separation of business and presentation layers  and certainly no Java code in templates  so you can generate templates directly from web presentation editing software  in most cases leveraging WYSIWYG   And certainly stay away of filters and pre and post processing  otherwise you may deal with support debugging difficulties since you always do not know where the variable gets the value

User · Answer

In order to avoid Java code in JSP files  Java now provides tag libraries  like JSTL  Also  Java has come up with JSF into which you can write all programming structures in the form of tags

User · Answer

Wicket is also an alternative which completely separates Java from HTML  so a designer and programmer can work together and on different sets of code with little understanding of each other  Look at Wicket

User · Answer

By using JSTL tags together with EL expressions  you can avoid this  Put the following things in your JSP page   lt    page contentType  quot text html charset UTF-8 quot  language  quot java quot    gt   lt    taglib uri  quot http   java sun com jsp jstl core quot  prefix  quot c quot    gt   lt    taglib uri  quot http   java sun com jsp jstl fmt quot  prefix  quot fmt quot    gt

User · Answer

Sure  replace  lt    counter      gt  by an event producer-consumer architecture  where the business layer is notified about the need to increment the counter  it reacts accordingly  and notifies the presenters so that they update the views  A number of database transactions are involved  since in future we will need to know the new and old value of the counter  who has incremented it and with what purpose in mind  Obviously serialization is involved  since the layers are entirely decoupled  You will be able to increment your counter over RMI  IIOP  SOAP  But only HTML is required  which you don t implement  since it is such a mundane case  Your new goal is to reach 250 increments a second on your new shiny E7  64GB RAM server   I have more than 20 years in programming  most of the projects fail before the sextet  Reusability Replaceability OO-ability Debuggability Testability Maintainability is even needed  Other projects  run by people who only cared about functionality  were extremely successful   Also  stiff object structure  implemented too early in the project  makes the code unable to be adapted to the drastic changes in the specifications  aka agile    So I consider as procrastination the activity of defining  layers  or redundant data structures either early in the project or when not specifically required   nbsp

User · Answer

Technically  JSP are all converted to Servlets during runtime  JSP was initially created for the purpose of the decoupling the business logic and the design logic  following the MVC pattern  So JSP is technically all Java code during runtime  But to answer the question  tag libraries are usually used for applying logic  removing Java code  to JSP pages

User · Answer

If we use the following things in a Java web application  Java code can be eliminated from the foreground of the JSP file   Use the MVC architecture for a web application  Use JSP Tags   a  Standard Tags b  Custom Tags  Expression Language

User · Answer

If somebody is really against programming in more languages than one  I suggest GWT  Theoretically  you can avoid all the JavaScript and HTML elements  because Google Toolkit transforms all the client and shared code to JavaScript  You won t have problem with them  so you have a webservice without coding in any other languages  You can even use some default CSS from somewhere as it is given by extensions  smartGWT or Vaadin   You don t need to learn dozens of annotations  Of course  if you want  you can hack yourself into the depths of the code and inject JavaScript and enrich your HTML page  but really you can avoid it if you want  and the result will be good as it was written in any other frameworks  I it s say worth a try  and the basic GWT is well-documented  And of course many fellow programmers hereby described or recommended several other solutions  GWT is for people who really don t want to deal with the web part or to minimize it

User · Answer

Use a Backbone js or AngularJS-like JavaScript framework for UI design and fetch the data using a REST API  This will remove the Java dependency from the UI completely

User · Answer

No matter how much you try to avoid  when you work with other developers  some of them will still prefer scriptlet and then insert the evil code into the project  Therefore  setting up the project at the first sign is very important if you really want to reduce the scriptlet code  There are several techniques to get over this  including several frameworks that other mentioned   However  if you prefer the pure JSP way  then use the JSTL tag file  The nice thing about this is you can also set up master pages for your project  so the other pages can inherit the master pages  Create a master page called base tag under your WEB-INF tags with the following content    lt   tag description  Overall Page template  pageEncoding  UTF-8   gt    lt   attribute name  title  fragment  true    gt    lt html gt     lt head gt       lt title gt            lt jsp invoke fragment  title  gt  lt  jsp invoke gt       lt  title gt      lt  head gt     lt body gt       lt div id  page-header  gt                   lt  div gt       lt div id  page-body  gt         lt jsp doBody  gt       lt  div gt       lt div id  page-footer  gt                   lt  div gt     lt  body gt   lt  html gt     On this mater page  I created a fragment called  title   so that in the child page  I could insert more codes into this place of the master page  Also  the tag  lt jsp doBody  gt  will be replaced by the content of the child page   Create child page  child jsp  in your WebContent folder         lt    taglib prefix  t  tagdir   WEB-INF tags    gt    lt t base gt       lt jsp attribute name  title  gt            lt bean message key  hello world    gt       lt  jsp attribute gt        lt jsp body gt       Put your content of the child here       lt  jsp body gt      lt  t base gt      lt t base gt  is used to specify the master page you want to use  which is base tag at this moment   All the content inside the tag  lt jsp body gt  here will replace the  lt jsp doBody  gt  on your master page  Your child page can also include any tag lib and you can use it normally like the other mentioned  However  if you use any scriptlet code here   lt    request getParameter  name     gt       and try to run this page  you will get a JasperException because  Scripting elements    amp lt      amp lt jsp declaration   amp lt      amp lt jsp expression   amp lt     amp lt jsp scriptlet   are disallowed here  Therefore  there is no way other people can include the evil code into the jsp file  Calling this page from your controller   You can easily call the child jsp file from your controller  This also works nice with the struts framework

User · Answer

Just use the JSTL tag and EL expression

User · Answer

JSTL offers tags for conditionals  loops  sets  gets  etc  For example    lt c if test    someAttribute     something    gt          lt  c if gt    JSTL works with request attributes - they are most often set in the request by a Servlet  which forwards to the JSP

User · Answer

There are also component-based frameworks  such as Wicket  that generate a lot of the HTML for you  The tags that end up in the HTML are extremely basic and there is virtually no logic that gets mixed in  The result is almost empty-like HTML pages with typical HTML elements  The downside is that there are a lot of components in the Wicket API to learn and some things can be difficult to achieve under those constraints

User · Answer

Using scriptlets in JSPs is not a good practice   Instead  you can use    JSTL tags    EL expressions Custom Tags- you can define your own tags to use    Please refer to     http   docs oracle com javaee 1 4 tutorial doc JSTL3 html EL

[java] How can I avoid Java code in JSP files, using JSP 2?

Examples related to java

Examples related to jsp

Examples related to scriptlet