JSP best practices...

I know that in the MVC model for web services/application design that the JSP is the view component and so therefore the idea is to take out all scripting code (except for JavaScript maybe). I was wondering if the best practice for using/writing JSPs is to have a servlet determine what action the user requests and then dynamically generating the JSP based on that action. I believe that this is what the Sun developers are doing with the index.jsp page for the forums section. They use a SessionServlet although for which purposes I am not entirly sure. I downloaded the index.jsp page to see if it had scripting code in it, but it was just a buch of HTML, so am I wrong to assume that it was dynamically generated? Any insight to this mystery would be much appreciated!

Normally you cant donwload JSP code.
You downloaded HTML that was generated by JSP

Similar Messages

JSP Best Practices and Oracle Report

Hello,
I am writing an application that obtains information from the user using a JSP/HTML form and then submitted to a database, the JSP page is setup using JSP Best Practices in which the SQL statments, database connectivity information, and most of the Java source code in a java bean/java class. I want to use Oracle Reports to call this bean, and generate a JSP page displaying the information the user requested from the database. Would you please offer me guidance for setting this up.
Thank you,
Michelle

JSP Best Practices.
More JSP Best Practices
But the most important Best Practice has already been given in this thread: use JSP pages for presentation only.

JSP best practices, tips?

let me know few tips and best practices on java server pages.. as i am working on jsp project

JSP Best Practices.
More JSP Best Practices
But the most important Best Practice has already been given in this thread: use JSP pages for presentation only.

Does JSP best practice of putting under WEB-INF apply to JSF pages?

I'm new to JSF and wondering if the "best practice" advice that used to be given of storing your jsp pages under WEB-INF (when using Model2) to keep them from being served up without going through your controller still applies with JSF.
Since the component lifecycle is so different, I'm wondering if it would still apply? If anyone can explain why it might or might not apply I'd appreciate it!
Thanks!

The rule is:
keep all the pages you don�t user to "browse", under the WEB-INF directory.
MeTitus

Best practice for dealing with Recordsets, JDBC and JSP?

I've spent the last three years developing web apps using JSP, Struts and Kodo JDO for persistence. All of the content for the apps was created as Java objects using model classes and saved to an Oracle db. Thus, data retrieved from the db was as instances of the model classes and then put into Struts form beans, etc.
I changed jobs last month and am now having to use Servlets with JDBC to retrieve records from db tables and returning it into Recordsets. Oh, and I can't use Struts in my JSPs either. I'm beginning to think that I had it easy at my previous job but maybe that's just because I was used to it.
So here are my problems/questions:
I have two tables with a one to many relationship that I need to retrieve data from, show in a jsp and be able to update eventually.
So here's what I am doing:
a) In a servlet, I use a SQL statement to join the tables and retrieve the results into a Recordset.
b) I created a class with a bunch of String attributes to copy the Recordset data into, one Recordset row per each instance of the bean and then close the Recordset
c) I then add the beans to an ArrayList and save the ArrayList into the session.
d) Then, in the JSP, I retrieve the ArrayList from the session and iterate over each bean instance, printing the data out to the jsp. There are some logic statements to determine when not to print redundant data caused by the one to many join.
e) I have not written the code to update the data yet but was planning on having separate jsps for updating the (one) table and the (many) table.
Would most of you do something similar? Would you use one SQL statement to retrieve all of the data for display and use logic to avoid printing the redundant part of the data? Or would you have used separate SQL queries, one for each table? Would you have saved the results into something other than an instance of a bean class that represents one record in the RecordSet? Would you have had a bean class with attributes other than Strings - like had a collection attribute to hold the results from the "many" table? The way that I am doing everything just seems so cumbersome and difficult compared to using Struts and JDO before.
Your help/opinion will be greatly appreciated!

Would you use one SQL statement to retrieve all of the data for display Yes.
and use logic to avoid printing the redundant part of the dataNo.
I believe in minimising the number of queries. If it is a simple one-many join on a db table, then one query is better than one + n queries.
However I prefer to store the objects in a bean class with attributes other than strings - ie one object, with a collection attribute to hold the related "many" records.
Does the fact you are not using Struts mean that you have to use scriptlet code? (shudder)
Or are you using JSTL, or other custom tags?
How about tools like Ant? Junit testing?
The way that I am doing everything just seems so cumbersome and difficult
compared to using Struts and JDO before.Anything different takes adjusting to. Sounds like you know what you're doing for the most part. I agree, in terms of best practices what you have described so far sounds like a step backwards from what you were previously doing.
However I wouldn't go complaining about it too loudly, too quickly. If you're new on the block theres nothing like making a pain of yourself, and complaining how backwards the work they have done is to put your new workmates' backs up
Look on it as a challenge. Maybe discuss it quietly with a team leader, to see if they understand how much easier/better/less error prone such approaches can be?
Struts, cumbersome as it can be, definitely has the advantage of pushing you to follow good MVC practice.
Good luck,
evnafets

Best JSP/Beans Practices

I am setting up a very simple guestbook using JSP. I have a GuestBean in which I set the info passed from the <form>. Is it best practice to have a separate bean for db connection and inserting the info or can I do it all in one bean?
If separate is the better route, do I add a <jsp:useBean> tag in my JSP page to instantiate an instance of the db connection/insert bean?
Input greatly appreciated....Thanks!

From my own expierence, the best way to handle database connections is to let the Web Container handle them. I usually have the bean do a JNDI lookup each time it needs a connection. This seperates the bean from any database connection logic. It also gives you the flexibility of changing eitehr the connection method or the database server without having to modify your bean code.
- Chris

Customize OIM jsp forms using xlWebApp.war: Best Practice?

Based on searching the forum, it appears that inflating the war files, making changes and putting them back again is the way to customize the jsp forms in OIM. Is this a best practice though? What happens when I want to upgrade? Do I lose all my customizations or is there another way to do this?
Edited by: user4486549 on Jun 5, 2009 5:11 AM

Hi,
That is the only way to do it.In case of upgrade every time you will have to merge the changes in new war file and redeploy it. Just take care of one thing that do not modify existing jsp or classes.Create your own jsps and classes.
Regards

Best Practices:: How to generate XML file from a ResultSet

Hi all,
Could someone please suggest the best practices of how to generate an XML file from a resultset? I am developing a web application in Java with Oracle database and one of my tasks is to generate an XML file when the user, for example, click a "download as XML" button on the JSP. The application is basically like an Order with line items. I am using Struts and my first thought has been to have an action class which will extend struts's DownloadAction and through StAX's Iterator API to create an XML file. I intend to have a POJO which will have properties of all columns of my order and line items tables so that for each order I get all line items and:
1. Write order details then
2. Through an iterator write line items of that order to an XML file.
I will greatly appreciate for comments or suggestions on the best way to do this through any pointers on the Web.
alex

Use a OracleWebRowSet in which an XML representation of the result set may be obtained.
http://www.oracle.com/technology/sample_code/tech/java/sqlj_jdbc/files/oracle10g/webrowset/Readme.html
http://download.oracle.com/docs/cd/B28359_01/java.111/b31224/jcrowset.htm

Best practices on number of pipelines in a single project/app to do forging

Hi experts,
I need couple of clarification from you regarding endeca guided search for enterprise application.
1)Say for example,I have a web application iEndecaApp which is created by imitating the jsp reference application. All the necessary presentation api's are present in WEB-INF/lib folder.
1.a) Do I need to configure anything else to run the application?
1.b) I have created the web-app in eclipse . Will I be able to run it from the any thirdparty tomcat server ? If not then where I have to put the war file to successfully run the application?
2)For the above web-app "iEndecaApp" I have created an application named as "MyEndecaApp" using deploymenttemplate. So one generic pipeline is created. I need to integrate 5 different source of data . To be precise
i)CAS data
ii)Database table data
iii)Txt file data
iv)Excel file data
v)XML data.
2.a)So what is the best practice to integrate all the data. Do I need to create 5 different pipeline (each for each data) or I have to integrate all the 5 data's in a single pipeline ?
2.b)If I create 5 different pipeline then all should reside in a single application "MyEndecaApp" or I need to create 5 difference application using deployment template ?
Hope you guys will reply it back soon..... Waiting for your valuable response ..
Regards,
Hoque

Point number 1 is very much possible ie running the jsp ref application from a server of your choice.I havent tried that ever but will draw some light on it once I try.
Point number 2 - You must create 5 record adapters in the same pipeline diagram and then join them with the help of joiner components. The resultant must be fed to the property mapper.
So 1 application, 1 pipeline and all 5 data sources within one application is what should be the ideal case.
And logically also since they all are related data, so must be having some joining conditions and you cant ask 5 different mdex engines to serve you a combined result.
Hope this helps you.
<PS: This is to the best of my knowledge>
Thanks,
Mohit Makhija

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

Best Practice for link to WebdynPro page in welcome page

Hi Experts,
I am new in SAP Portal. I need some guidance from you guys. I have a requirement to create welcome page which is JSP and has a link to a WebdynPro page. I have to put the url in JSP file. So i do not know what kind of URL i should put in the JSP.
The problem is if i put the url which i can see in the address bar like 'http://DevServer/WebDynPro/ApplcationA', when i transport it to another server ,for example Production,. The real url might be change to 'http://ProdServer/WebDynPro/ApplcationA'. It may cause the link in JSP can not be worked.
I would like to ask you the best practice for this case. What url? What configuration?
Thank you in advance,
Noppong Jinbunluphol
P.S. For the JSP, i create it in portal application dc.

Dear Noppong,
You can do it with multiple ways like :-
1. Get the current host name and make complete URL with using host name for the webdynpro iview.
request = (IPortalComponentRequest) this.getRequest();
HttpServletRequest req = request.getServletRequest();
StringBuffer strURL = req.getRequestURL();
2. Create the KM Document or Link for webdynpro Iview OR Create the WPC Web Page for the webdynpro ivew
Refer to [http://help.sap.com/saphelp_nw70/helpdata/en/06/4776399abf4b73945acb8fb4f41473/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/06/4776399abf4b73945acb8fb4f41473/frameset.htm]
[http://help.sap.com/saphelp_nw70/helpdata/en/06/4776399abf4b73945acb8fb4f41473/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/06/4776399abf4b73945acb8fb4f41473/frameset.htm]
[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ff/681a4138a147cbabc3c76bde4dcdbd/content.htm|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ff/681a4138a147cbabc3c76bde4dcdbd/content.htm]
Hope it will helps
Best Regards
Arun Jaiswal

Best practice for application module for scalability

if i compare application module with forms 6i runtime session.(correct me if i wrong)
In forms 6i, we create for single form for purchase entry. in which we select table like po , po_item, item_master, customer master
also single form for sales entry. in which we select table like sales , sales_item, item_master, customer master, po , po_item
So my question is. in jdeveloper , we planning to make separate jsp page and applicaiton module for purchase entry,
separare jsp page and application module for sales.
is it ok.
or
what is the best practice in this senario.?? ( or in scalability senario)
if i made one single application module for whole application (let say 300 entity's(tables)) will performance of my app server degrade.

You might want to read the chapter about AM Granularity in the ADF Developer Guide:
http://download.oracle.com/docs/html/B25947_01/bcservices009.htm#sm0229

What are best practice for packaging and deploying j2EE apps to iAS?

We've been running a set of J2EE applications on a pair of iAS SP1b for about a year and it has been quite stable.
Recently however we have had a number of LDAP issues, particularly when registering and unregistering applications (registering ear files sometimes fails 1st time but may work 2nd time). Also We've noticed very occasionally that old versions of classes sometimes find their way onto our machines.
What is considered to be best practice in terms of packaging and deployment, specifically:
1) Packaging - using the deployTool that comes with iAS6 SP1b to package is a big manual task, especially when you have 200+ jsp files. Are people out there using this or are they scripting it with a build tool such as Ant?
2) Deploying an existing application to multiple iAS's. Are you guys unregistering old application then reregistering new application? Are you shutting down iAS whilst doing the deployment?
3) Deploying ear files can take 5 to 10 mins, is this normal?
4) In a clustered scenario where HTTPSession is shared what are the consequences of doing deployments to data stored in session?
thanks in asvance for your replies
Owen

You may want to consider upgrading your application server environment to a newer service pack. There are numerous enhancements involving the deployment tool and run time layout of your application that make clear where you're application is loading its files from.
If you've at a long running application server environment, with lots of deployments under your belt, you might start to notice slow downs in deployment and kjs start time. Generally this is due to garbage collecting in your iAS registry.
You can do several things to resolve this. The most complete solution is to reinstall the application server. This will guarantee a clean ldap registry. Of course you've got to restablish your configurations and redeploy your applications. When done, backup your application server install space with the application server and directory server off. You can use this backup to return to a known configuation at some future time.
For the second method: <B>BE CAREFUL - BACKUP FIRST</B>
There is a more exhaustive solution that involves examining your deployed components to determine the active GUIDS. You then search the NameTrans section of the registry searching for Applogic Servlet *, and Bean * entries that represent your previously deployed components but are represented in the set of deployed GUIDs. Record these older GUIDs, remove them from ClassImp and ClassDef. Finally remove the older entries from NameTrans.
Best practices for deployment depend on your particular environmental needs. Many people utilize ANT as a build tool. In later versions of the application server, complete ANT scripts are included that address compiling, assembly and deployment. Ant 1.4 includes iAS specific targets and general J2EE targets. There are iAS specific targets that can be utilized with the 1.3 version. Specialized build targets are not required however to deploy to iAS.
Newer versions of the deployment tool allow you to specify that JSPs are not to be registered automatically. This can be significant if deployment times lag. Registered JSP's however benefit more fully from the services that iAS offers.
2) In general it is better to undeploy then redeploy. However, if you know that you're not changing GUIDs, recreating an existing application with new GUIDs, or removing registered components, you may avoid the undeploy phase.
If you shut down the KJS processes during deployment you can eliminate some addition workload on the LDAP server which really gets pounded during deployment. This is because the KJS processes detect changes and do registry loads to repopulate their caches. This can happen many times during a deployment and does not provide any benefit.
3) Deploying can be a lengthy process. There have been improvements in that performance from service pack to service pack but unfortunately you wont see dramatic drops in deployment times.
One thing you can do to reduce deployment times is to understand the type of deployment. If you have not manipulated your deployment descriptors in any way, then there is no need to deploy. Simply drop your newer bits in to the run time space of the application server. In later service packs this means exploding the package (ear,war, or jar) in to the appropriate subdirectory of the APPS directory.
4) If you've changed the classes of objects that have been placed in HTTPSession, you may find that you can no longer utilize those objects. For that reason, it is suggested that objects placed in session be kept as simple as possible in order to minimize this effect. In general however, is not a good idea to change a web application during the life span of a session.

Select One Choice attribute' LoV based on two bind variables, best practice

Hello there,
I am in the process of learning the ADF 11g, I have following requirement,
A page must contain a list of school names which is needed to be fetched based on two parameters, the parameters are student information been inserted in the previous page.
I have defined a read only view "SchoolNamesViewRO", it's query depends on two bind variables :stdDegree and stdCateg.
added that RO View as a view accessor to the entity to which the name attribute belongs, and then add LoV for the name attribute using the ReadOnly view,
added the name attribute as Select One Choice to page2,
and now I need to pass the values of the bind variables of the ReadOnly view,
the information needed to be passed as the bind variables is inserted in the previous page, I could have the data as bindings attribute values in the page2 definition
I have implemented the next two appraoches but both resulted in an empty list :
* added ExecuteWithParams Action to the bindings of the page and then defined an Invoke Action (set refresh condition) in the executable s, set the default values of the parameters to be the attributes values' input value,
in the trace I code see that the binding fetches correct values as supposed , but the select list appears empty, does the this execution for the query considered to be connected to the list ?
* added a method to the ReadOnly view Imp java class to set the bind variables, then I define it as a MethodAction in the bindings , and then create an Invoke action for it , also the select is empty,
if the query been executed with the passed variables, then why the list is empty? is it reading data from another place than the page!
and what is the best practice to implement that requirement?
would the solution be : by setting the default value of the bind variables to be some kind of Expression!
please notice that query execution had the bound variables ( I see in the trace) are set to the correct values.
would you give some hints or redirect me to a useful link,
Thanks in advance
Regards,

please give me any example using backing bean .for example
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1">
<af:form id="f1">
<af:selectOneChoice label="Label 1" id="soc1" binding="#{Af.l1}"
autoSubmit="true">
<af:selectItem label="A" value="1" id="si1"/>
<af:selectItem label="B" value="2" id="si2"/>
</af:selectOneChoice>
<af:selectOneChoice label="Label 2" id="soc2" disabled="#{Af.l1=='2'}"
partialTriggers="soc1">
<af:selectItem label="C" value="3" id="si3"/>
<af:selectItem label="D" value="4" id="si4"/>
</af:selectOneChoice>
</af:form>
</af:document>
</f:view>
</jsp:root>
package a;
import oracle.adf.view.rich.component.rich.input.RichSelectOneChoice;
public class A {
private RichSelectOneChoice l1;
public A() {
public void setL1(RichSelectOneChoice l1) {
this.l1 = l1;
public RichSelectOneChoice getL1() {
return l1;
is there any mistake

Best Practices?

I have an application which has several EJBs that make JDBC connections.
What is considered best practice for passing parameters like class, url,
username and password to these EJBs? The basic structure is a servlet which
uses one class that makes all the calls to the EJBs. I've come up with a
couple ideas for passing these JDBC parameters around. Have I missed any
thing and what are the pros/cons of each?
1. Read <init-param> from WEB-INF/web.xml for the servlet. Pass these to
the helper/wrapper class, which then passes them to all of the EJBs.
2. Specify all the parameters in META-INF/ejb-jar.xml for each EJB.
3. Somehow specify these parameters on a global or application level on the
application server and have all EJBs use these.
#1 seems like it should work, but also seems awkward, as business logic is
now on the web side. Also, database connection data would be passed across
the firewall between the web and app server. Is this a security risk?
#2 will work, but changes to our JDBC pool would require changing the
META-INF/ejb-jar.xml for each EJB.
#3 sounds the best to me, as no database information is passed though
between the app and web server and we would only have to change the
parameters in one location to get all EJBs to now connect to the new JDBC
pool. How can this be implemented?
On a related note, what's the difference between a <contex-param> and
<env-entry> in the WEB-INF/web.xml? We are using <contex-param> to read a
URL for our JSPs for image locations, while we are using <env-entry> to read
in the URL to our application server.
Thanks,
Eric

I believe you already posted this question in a different newsgroup. Please
only post in one newsgroup.
Peace,
Cameron Purdy
Tangosol Inc.
<< Tangosol Server: How Weblogic applications are customized >>
<< Download now from http://www.tangosol.com/download.jsp >>
"Eric Fenderbosch" <[email protected]> wrote in message
news:3b86afae$[email protected]..
I have an application which has several EJBs that make JDBC connections.
What is considered best practice for passing parameters like class, url,
username and password to these EJBs? The basic structure is a servletwhich
uses one class that makes all the calls to the EJBs. I've come up with a
couple ideas for passing these JDBC parameters around. Have I missed any
thing and what are the pros/cons of each?
1. Read <init-param> from WEB-INF/web.xml for the servlet. Pass these to
the helper/wrapper class, which then passes them to all of the EJBs.
2. Specify all the parameters in META-INF/ejb-jar.xml for each EJB.
3. Somehow specify these parameters on a global or application level onthe
application server and have all EJBs use these.
#1 seems like it should work, but also seems awkward, as business logic is
now on the web side. Also, database connection data would be passedacross
the firewall between the web and app server. Is this a security risk?
#2 will work, but changes to our JDBC pool would require changing the
META-INF/ejb-jar.xml for each EJB.
#3 sounds the best to me, as no database information is passed though
between the app and web server and we would only have to change the
parameters in one location to get all EJBs to now connect to the new JDBC
pool. How can this be implemented?
On a related note, what's the difference between a <contex-param> and
<env-entry> in the WEB-INF/web.xml? We are using <contex-param> to read a
URL for our JSPs for image locations, while we are using <env-entry> toread
in the URL to our application server.
Thanks,
Eric

JSP best practices...

Similar Messages

Maybe you are looking for