Uploaded image for project: 'YesCart'
  1. YesCart
  2. YC-383

Use of statefull components in Wicket forces page to become statefull

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1.0
    • Component/s: sf web
    • Labels:
      None

      Description

      It was noticed that we have session creation in unexpected places (JSESSIONID cookie is created)

      As per this blog: http://blog.armstrongconsulting.com/?p=14
      It seems that stateless pages become statefull if we use Forms - because forms are statefull components.

      Top prevent this we need to use StatelessForm instead of Form components in all of our pages.

      Also please apply the checkIfPageStateless() check in development mode only to list all the components that make page stageful again.
      Use ShopContext.getLog(this) logger for this, please.
      (Need to use isPageStateless() check as per http://stackoverflow.com/questions/14364340/stateless-wicket-page-still-having-page-version-url-parameter-appended-how-to)

      This fix will require a full scale regression testing of checkout functionality.

      Some examples for wicket stateless forms:
      http://www.wicket-library.com/wicket-examples/stateless/foo?-1.IFormSubmitListener-statelessform

        Attachments

          Activity

            People

            • Assignee:
              denis.lozenko Denis Lozenko (Inactive)
              Reporter:
              denis Denis Pavlov
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: