Skip to Content
author's profile photo Former Member
Former Member

HTMLB location: in Java code vs. JSP

HTMLB controls can be instantiated in the Java code (say in class derived from DynPage) or can be created by using taglibs in JSP. The question is what the preferred way is and what are pros and cons?  In general if it is not necessary to use on the page HTML or JavaScript there is no necessity to have JSP at all. The issue is that JSP is the mixture of three things Java code, HTML, and JavaScript. This mixture is difficult to support and SUN acknowledges this by saying that it is better to have Java code in the taglibs. In addition to this combination Java code, HTML, and JavaScript is difficult to debug. At the same time pure Java code can be debugged without any problems. The bottom line is there some guidelines/recommendations that identify when it is better to use DynPage with HTMLB components instantiated directly in the vs. DynPage/JSPDynPage with JSP? Any input on this issue will be appreciated. Thank you.

Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Posted on Jan 23, 2004 at 07:40 PM

    At the end it is a matter of taste.

    Using Portal Components instead of JSP has some advantages:

    In PC you have mor functionality. JSP  Taglibs have in general less features.

    JSP development is faster if you make no mistakes , but  no support through the IDE in general.



    Add comment
    10|10000 characters needed characters exceeded