Difference between jsp:forward and logic:forward

Hi,
Can anyone let me know??
what is the difference between <jsp:forward> in and <logic:forward> in struts
Thanks in advance,
Regards
Dhinesh kumar R

See: http://java.oreilly.com/news/jsptips_1100.html (number 4)

Similar Messages

  • Difference between jsp:forward sendRedirect and jsp include directive

    Am very much confused, please explain me the difference between
    jsp:forward sendRedirect and jsp include directive with a suitable example.
    I'll be very gratefull. Its very urgent.

    One basic difference. The include executes in the .jsp servelet created. The redirect transfers "control" by redirecting the client request to another destination. In other words, the current .jsp is no longer in charge or in the calling chain in any way.

  • Difference between jsp forward tag and sendRedirect

    I would like to know the difference between jsp forward tag and sendRedirect.
    Please explain with a suitable example if possible ...
    glenn

    See: http://java.oreilly.com/news/jsptips_1100.html (number 4)

  • What is the difference between jsp :include and server side include

    what is the difference between jsp :include and server side include(request dispatcher include method)????
    i understand that both request dispatcher include method and jsp:include take dynamic data,so when would one use request dispatcher include and when jsp:include.
    Is the usage interchangeable?i believe jsp include is used only for jsp/html but include directive can be used to include servlets ,jsp and html....correct me if i m wrong and
    do suggest if u hav ny other diff in this context...

    The difference really is: in what format do you want your inclusions? If your environment has many Java developers and only a few designers that focus mainly on, say, Flash, that might push you more towards the server-side include() directive. Or, if you have a large set of pages that receive dynamic content that is displayed in a consistent fashion (such as a workflow header area on a page).
    If, on the other hand, you have more web designers, there may be a greater desire to deal in markup rather than Java code. Java developers themselves might prefer to view markup (JSP) that more resembles the eventual output than something occuring in Java code.
    Finally, there are considerations of tiering. While it is totally possible to (and I have previously) implement 'view classes' that render markup or generate layout templates, JSP's offer, IMO, a subtle, psychological advantage. By forcing a developer to work in a different format, markup versus Java source, the separation on view from controller and model becomes a bit easier. It is still possible to make mistakes, but if a developer at some point notices, "Wait, I'm in a JSP, should I be importing a java.sql class?", then the choice to use JSP includes has paid off in spades.
    - Saish

  • Difference between physical join and logical join

    Hi Gurus,
    Can anyone tell me what is the difference between physical join and logical join
    Thanks,
    Chandra

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables. Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join, you just tell it that there is a relationship between these two logical entities. When the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    In BMM you use complex joins to establish which logical tables are joined which another, the OBI EE server will go to the physical level to search the physical join to make the query. You can also use physical joins in the BMM to override the join in the physical layer but only in very specific conditions.
    If you also set complex join in the physical layer OBI EE won't be able to construct the physical query.
    Hope this answers your question.
    Award points if helpful.
    Thanks,
    -Amith.

  • Difference between jsp:include and %@ include

    what is the difference between <jsp:include> and <%@ include %>? which has better performance? When to use which? suppose i have a menu that should be included in every page, which should I use?
    Thank you
    Cal

    <%-- some date this page was last updated with that particular version of JSP file --%>
    <% include file="relative URL" %>
    You use the include directive, as indicated, to include a file in the main JSP file at the time the file is translated into a servlet. This is done at translation time and therefore if the included JSP file changes, all the JSP files that use this included file will need tobe updated. If you use this include statement then i would suggest that you add a date descriptor of the last time it was modifed so that you can go back and tell if you have updated a particular JSP file or not.
    <jsp:include page="relative url" flush = "true" />
    When you use the JSP descriptor like this, you are getting the requested JSP file at REQUEST time and therefore you do not hae to worry about updating the calling JSP page.
    Hope this helps

  • Is there any difference between "jsp:useBean" and "scriptlet" ?

    A few days ago, I asked similar question. But I didn't get the answer I wanted.
    I want to know the differnce between <jsp:useBean../> and <% .. %>(scriptlet).
    I tested in three environments(Oracle Jserv, OC4J, and Apache Tomcat).
    In Oracle Jserv and OC4J, a problem occured. But, Apache Tomcat does not occur a problem.
    For example,
    1) TestClass.java (Bean)
    public class TestClass {
    private String txt;
    public class TestClass {
    txt = "Test"; ----- (g
    public String getTxt() {
    return txt;
    2) test.jsp
    <html><body>
    <% TestClass test = new TestClass(); %> ---(h
    <%= test.getTxt() %>
    </body></html>
    Assume that I visit "http://localhost:8888/test.jsp".
    In Tomcat, if I change "Test"(number(g) to "Test1" and compile the browser shows the change.
    But Oracle Jserv and OC4J does not do that. They also show the old String.
    So, I changed <% TestClass test = new TestClass(); %>(number(h) to <jsp:useBean id="test" class="TestClass" />. That is, I changed "Scriptlet" to "JSP useBean Tag".
    Then, Oracle Jserv and OC4J also show the changes.
    To conclude, is there any difference between "JSP useBean Tag" and "Scriptlet"?
    Can't I use a scriptlet (to make a class) in Oracle Servlet Engine?
    Thanks.

    It could be as simple as the JSP not recompiling between java recompiles - ie, it compiles in the link to the old class.
    Try changing the JSP file (add and delete a space) after you change the java code, and then see what happens.
    Jonny
    null

  • Difference between jsp forward action tag and response.forward()

    hi guys
    i have just started programming using j2ee technology.
    could anyone please tell me what is the difference between the jsp forward action tag and froward method using the response object?

    There really isn't one. The JSP forward tag is a convenience tag for JSP, that uses the response method.

  • Difference between client system and logical system

    Hi all
    Can any one explain about the client system and logical system??
    When this message type will comes in to picture at the time idoc processing??
    Thanks and Regards
    Arun Joseph

    hi Arun,
    I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
    and to know the diffrence between client and logical system very keenly go thru this link
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
    IDOC Administration
    Step 1: Tcode: WE 46
    Setting the Global Parameter for IDOC Interface
    Step 2: Maintaing a Logical System
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Define Logical systems
    Go to Spro transaction
    Step 3: Allocating Logical systems to the Client
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Logical Systems, Assign Client to Logical systems
    Go to Spro transaction
    Step 4: Setting up an RFC destination
    Tcode: SM 59
    Path: From the ALE Customizing in IMG, choose Communication, Define RFC
    Destination
    You can also do the Advanced Settings in the RFC Destination
    Step 5: The PORT definition
    TCode: WE 21
    Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
    Systems in Network, Asynchronous Processing, Assign Ports, Define Port
    Step 6: Generating Partner Profiles
    TCode: BD 82
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
    Step 7: Distributing the Model
    TCode: BD 64
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, Maintain Distribution Model and Distribute Views
    Technques for Distributing the Master Data:
    Technique 1: The Push Approach
    Executing the Process:
    TCode: BD 10
    Path: from the ALE Main Menu, choose Material Data Distribution, Cross
    Application, Material, Send
    Technique 2: The Change Pointer Technique
    Enable Change Pointers Globally
    TCode: BD 61
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers
    Enable Change Pointers Globally
    TCode: BD 50
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution, Replication of Modified Data, Activate
    Change Pointers for Message Type
    Specify the Fields for which Change Pointers are to be written
    TCode: BD 52
    Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
    Change-Relevant Fields
    How the Classification system works:
    Creating a Class Type
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Status for the Class Types:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classification Status:
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
    Maintaing Classes:
    TCode: CL 01 (it is zero)
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
    Allocating classes to the Logical Syatems
    TCode: BD 68
    TCode: O1 CL(it is CAPITAL O)
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Distribution using Object Classes, Assign classes
    to Logical systems
    Filering at the IDOC level:
    Identify the Filter Object:
    TCode: BD 59
    Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
    Type to IDOC Field
    Modify the Distribution model
    How Segment Filtering Works:
    Configuration:
    Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
    TCode: BD 56
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
    The Reduced IDOC Type:
    The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
    The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
    represented by a forward slash(/) in the field.
    TCode: BD 53
    Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
    Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
    Create Reduced Message Type
    IDOC:
    Complete Documentaion on any IDOC using TCode: WE 60
    IDOC Display Tool: TCode: WE 02 or WE 05
    IDOC DEfinition components:
    Segment Components:
    1. Segment Type (E1, Z1)
    2. Segment Definition(E2, Z2)
    3. Segment Documentation(E3, Z3)
    E- SAP Defined
    z- Custom Defined
    IDOC runtime componets:
    control Record:
    Data Record:
    Staus Record:
    First Create the Segments using TCode: WE 31
    and then create the IDOC using TCode: We3 30
    first release the segments and then IDOC.
    Creating a new Basic IDOC Type:
    STEP 1: Analyze the Data:
    STEP 2: Create Data Elements:
    STEP 3: Create Segments:
    STEP 4: Create Basic IDOC Type:
    1. Execute TCode: WE 30
    2. Select the Create new option and enter a description for your basic IDOC type
    3. click the IDOC name, and click the create icon.
    Enter the segment type and its attributes.
    4. Keep on adding the segments as in step 3.
    5. Save the basic IDOC type
    Step 5: Release the Segment Type and Basic IDOC Type
    STEP 6: Transport the Segments and Basic IDOC Type
    Extending a Basic IDOC type:
    STEP 1: Analyze the Data:
    STEP 2: Create Custom Segments:
    STEP 3: Create the IDOC Type:
    STEP 4: Release the custom Segment and IDOC Extension
    Develop the function module for fteching the Data and then inserting the data into IDOC using
    EDIDD(for control Record) and EDIDC table(for DATA Record)
    Configuring the Systen for IDOCs
    Configure an Outboubd Process that uses Message Control
    Step 1: Create a new Message Type
    TCode: We 81
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 2: link the IDOC type to the Message Type
    TCode: We 82
    Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
    Step 3: Create a new Process Code
    TCode: We 41
    Path: From the Area menu of EDI, choose Control,Outbound Process COde
    Step 4: Create or Change a Partner Profile
    TCode: We 41
    Path: From the Area menu of EDI, choose IDOC,Partner Profile
    Configure an Outboubd Process for Stand-Alone Programs
    1. Create a new message type
    2. Link the IDOC type to the Message Type
    3. Add the message to the ALE Distribution Model(use BD 64)
    4. Create or change the Partner Profile
    go through the following site to have screen shots.
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    thanks
    karthik
    reward me points if usefull

  • Whats the difference between *.jsp and *.jspx

    Hi
    When I create a new jsf page the first step prompts me for the "type". I am wondering what is the difference between JSP Page and JSP Document? Which should I be using? Are there any white papers or documents that explain the advantages of each?
    Also, someone suggested that I use Facelets, has anyone else used these from inside jdeveloper? Any thoughts / tips would be appreciated.
    Thanks
    troy

    JSPX uses an XML doument for you page code - it is the way we recommend you build your page. Makes for cleaner code and easier customization.
    JSP uses HTML with embedded JSF tags in it.

  • Differences between (response.sendRedirect and Requestdispatcher.forward)

    Hi All,
    I have 3 queries
    *1> I wanted to know the "Differences" between*
    response.sendRedirect and Requestdispatcher.forward
    *2> when do we Opt for response.sendRedirect?*
    *3> when do we Opt for Requestdispatcher.forward?*
    Thanks,
    Deepak AL

    The fundamental difference is that sendRedirect is a client based direction, while forward is a server based one.
    SendRedirect forces the client to make a new request. In effect you are telling the client browser "What you are looking for is over there"
    RequestDispatcher forward, is purely an internal server transition. The client knows nothing about the forward happening.
    Example
    Lets say you request the page www.myserver.com/myPage.jsp
    Example A: Redirect
    We send a redirect to www.myserver.com/thatPageOverThere.jsp
    The browser receives this message, and its address url changes to www.myserver.com/thatPageOverThere.jsp, and it sends a new request over there.
    Note that it is a completely new request, so any parameters that were sent with the old request are irrelevant. If you want to send them again you have to put them into the sendRedirect url.
    You can also send a redirect to www.myOtherServer.com/thatPageOnACompletelyDifferentServer.jsp
    Example B: Forward to thatPageOverThere.jsp
    We obtain a request dispatcher to "thatPageOverThere.jsp" and forward to that resource.
    The server instead of running myPage.jsp now executes and returns thatPageOverThere.jsp
    The client browser knows nothing of this. As far as it knows it asked for myPage.jsp, and it is getting that response back.
    So if you forward to something like "my/page/inASubFolder.jsp" you have to be very careful with relative links on the page.
    The browser requested myPage.jsp, so it will resolve relative links from that Url.
    When to use one or the other?
    Redirect would need to be used when the resource is on another server.
    Another common usage is the "Post-Redirect-Get" pattern. (you might want to look that up)
    Hope this helps you understand a little.
    cheers,
    evnafets

  • Difference Between Port Forwarding and Port Triggering.

    Hi guys,
    I'm lost! The differences between port forwarding and port triggering is driving me nuts! It all seems very subtle to me. Can anyone explain to me (in a very simple way) what exactly are their differences. Thanks in advance!!

    Port Forwarding
    The big difference between this and port triggering is that forwarding is fixed.. you forward a port and it is always forwarded.. IE available to connection.. basically the forwarded port is excluded from the fire walling abilities of the router.  Second it is static and applies to one machine only. Whereas you could set port triggering to the router and thereafter any machine on the LAN can trigger it unless its already in use.. port forwarding must be specified for each individual machine.
    Port forwarding requires you to give each PC on the network its own unique static IP address.. Although there is ssh port forwarding that can be set dynamically. Most users only have the option of static ip port forwarding.
    The real downside of port forwarding is that it can be very tricky to set up... You may have to allow a series of ports on a machine and have to do that for each machine you want to allow through. Also routers often have limited abilities and may not allow you the ability to forward a port or select the service you require.
    Port Triggering
     This is a way of Dynamically assigning a service to a port WHEN it is required by an outgoing service. The port is initially not allowed so nothing can get in and you are protected by your network.  
    A good example of this is when using Yahoo! voice .. the voice works fine for a few minutes after you connect to Yahoo! then Yahoo! sends some kind of packet that requires a response from your PC... The packet is allowed in through your router no prob but the outgoing reply is not authorized to open a port on the router and is thus blocked. 
    'ope this helps

  • Difference between GENERAK TASK and GENERAL FORWARDING ALLOWED??

    Hi,
    Can anybody explain whats the actuall difference between GENERAL TASK and GENERAL FORWARDING ALLOWED.
    Both option allows to forward the workitem to any user. So what makes them difference?
    Thanks

    Hi,
    look here :
    [http://help.sap.com/saphelp_dimp50/helpdata/En/c5/e4b535453d11d189430000e829fbbd/content.htm]
    regards

  • What's the difference between jsp and jsf?

    who can tell me what's the difference between jsp and jsf?
    I'm puzzled when I found some of the technology in jsp is so similar to the ones in jsp( javaserver page)

    Hi,
    Find the difference between JSP and JSF
    1. A developer has more control with JSP, but (should) get easier development with JSF
    2. Event handling is done differently in JSP (HTTP) and JSF (Java)
    3. The UI is designed differently (or should be at least) with JSP (markup) and JSF (components).
    4. The end product should also be defined differently - JSP page versus a JSF application.
    Is this the only thing that is need to make a decision for either or? Probably not. There are other pieces that need to be taken in account when deciding which technology to use - tools support, enough components, type of application etc.... At this point there are not enough JSF components (although there are some interesting projects underway - Ajaxfaces, Myfaces, ADF Faces, and WebChart 3d) and enterprise tools support is still limited to a few tools vendor. Looking at our ADF Faces components they are currently available as early access (not production) and demands for these components are stacking up, literally, outside my office doorstep. Although I would love to make them production - now! - it is not a viable solution since we are still checking features and fixing critical bugs.
    All this combined - not enough enterprise level components in production, lacking tools support etc... - leave customers in a vacuum where the decision is either to continue with JSP, since it is mature and has a wide developer base, or move forward with JSF not sure if the support, or the developers will be there. This is particularly sensitive to customers that need to get started now and be production by summer.
    If you are in this vacuum here are some key points promoting JSF:
    1. Fundamental unit is the Component
    2. Built in event and state management
    3. Component sets can be provided by any vendor
    4. Closer to ASP.Net or Swing development
    5. Choice of UI technology
    6. Scale up (rich clients)
    7. Scale down (mobile devices)
    8. Built into J2EE containers in J2EE 5.0 (tentative)

  • Question about main difference between Java bean and Java class in JSP

    Hi All,
    I am new to Java Bean and wonder what is the main difference to use a Bean or an Object in the jsp. I have search on the forum and find some post also asking the question but still answer my doubt. Indeed, what is the real advantage of using bean in jsp.
    Let me give an example to illustrate my question:
    <code>
    <%@ page errorPage="errorpage.jsp" %>
    <%@ page import="ShoppingCart" %>
    <!-- Instantiate the Counter bean with an id of "counter" -->
    <jsp:useBean id="cart" scope="session" class="ShoppingCart" />
    <html>
    <head><title>Shopping Cart</title></head>
    <body bgcolor="#FFFFFF">
    Your cart's ID is: <%=cart.getId()%>.
    </body>
    <html>
    </code>
    In the above code, I can also create a object of ShoppingCart by new operator then get the id at the following way.
    <code>
    <%
    ShoppingCart cart = new ShoppingCart();
    out.println(cart.getId());
    %>
    </code>
    Now my question is what is the difference between the two method? As in my mind, a normal class can also have it setter and getter methods for its properties. But someone may say that, there is a scope="session", which can be declared in an normal object. It may be a point but it can be easily solved but putting the object in session by "session.setAttribute("cart", cart)".
    I have been searching on this issue on the internet for a long time and most of them just say someting like "persistance of state", "bean follow some conventions of naming", "bean must implement ser" and so on. All of above can be solved by other means, for example, a normal class can also follow the convention. I am really get confused with it, and really want to know what is the main point(s) of using the java bean.
    Any help will be highly apprecaited. Thanks!!!
    Best Regards,
    Alex

    Hi All,
    I am new to Java Bean and wonder what is the main
    difference to use a Bean or an Object in the jsp. The first thing to realize is that JavaBeans are just Plain Old Java Objects (POJOs) that follow a specific set of semantics (get/set methods, etc...). So what is the difference between a Bean and an Object? Nothing.
    <jsp:useBean id="cart" scope="session" class="ShoppingCart" />
    In the above code, I can also create a object of
    ShoppingCart by new operator then get the id at the
    following way.
    ShoppingCart cart = new ShoppingCart();
    out.println(cart.getId());
    ...Sure you could. And if the Cart was in a package (it has to be) you also need to put an import statement in. Oh, and to make sure the object is accessable in the same scope, you have to put it into the PageContext scope. And to totally equal, you first check to see if that object already exists in scope. So to get the equivalant of this:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart"/>Then your scriptlet looks like this:
    <%@ page import="my.pack.ShoppingCart %>
    <%
      ShoppingCart cart = pageContext.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        pageContext.setAttribute("cart", cart);
    %>So it is a lot more work.
    As in my mind, a normal class can also
    have it setter and getter methods for its properties.True ... See below.
    But someone may say that, there is a scope="session",
    which can be declared in an normal object.As long as the object is serializeable, yes.
    It may be
    a point but it can be easily solved but putting the
    object in session by "session.setAttribute("cart",
    cart)".Possible, but if the object isn't serializable it can be unsafe. As the point I mentioned above, the useBean tag allows you to check if the bean exists already, and use that, or make a new one if it does not yet exist in one line. A lot easier than the code you need to use otherwise.
    I have been searching on this issue on the internet
    for a long time and most of them just say someting
    like "persistance of state", "bean follow some
    conventions of naming", "bean must implement ser" and
    so on. Right, that would go along the lines of the definition of what a JavaBean is.
    All of above can be solved by other means, for
    example, a normal class can also follow the
    convention. And if it does - then it is a JavaBean! A JavaBean is any Object whose class definition would include all of the following:
    1) A public, no-argument constructor
    2) Implements Serializeable
    3) Properties are revealed through public mutator methods (void return type, start with 'set' have a single Object parameter list) and public accessor methods (Object return type, void parameter list, begin with 'get').
    4) Contain any necessary event handling methods. Depending on the purpose of the bean, you may include event handlers for when the properties change.
    I am really get confused with it, and
    really want to know what is the main point(s) of
    using the java bean.JavaBeans are normal objects that follow these conventions. Because they do, then you can access them through simplified means. For example, One way of having an object in session that contains data I want to print our might be:
    <%@ page import="my.pack.ShoppingCart %>
    <%
      ShoppingCart cart = session.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        session.setAttribute("cart", cart);
    %>Then later where I want to print a total:
    <% out.print(cart.getTotal() %>Or, if the cart is a JavaBean I could do this:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session"/>
    Then later on:
    <jsp:getProperty name="cart" property="total"/>
    Or perhaps I want to set some properties on the object that I get off of the URL's parameter group. I could do this:
    <%
      ShoppingCart cart = session.getAttribute("cart");
      if (cart == null) {
        cart = new ShoppingCart();
        cart.setCreditCard(request.getParameter("creditCard"));
        cart.setFirstName(request.getParameter("firstName"));
        cart.setLastName(request.getParameter("lastName"));
        cart.setBillingAddress1(request.getParameter("billingAddress1"));
        cart.setBillingAddress2(request.getParameter("billingAddress2"));
        cart.setZipCode(request.getParameter("zipCode"));
        cart.setRegion(request.getParameter("region"));
        cart.setCountry(request.getParameter("country"));
        pageContext.setAttribute("cart", cart);
        session.setAttribute("cart", cart);
      }Or you could use:
    <jsp:useBean id="cart" class="my.pack.ShoppingCart" scope="session">
      <jsp:setProperty name="cart" property="*"/>
    </jsp:useBean>The second seems easier to me.
    It also allows you to use your objects in more varied cases - for example, JSTL (the standard tag libraries) and EL (expression language) only work with JavaBeans (objects that follow the JavaBeans conventions) because they expect objects to have the no-arg constuctor, and properties accessed/changed via getXXX and setXXX methods.
    >
    Any help will be highly apprecaited. Thanks!!!
    Best Regards,
    Alex

Maybe you are looking for