Uploaded image for project: 'Struts 2'
  1. Struts 2
  2. WW-3574

Problem using JSP expression with Struts 2.0.14 while migrating from Struts 1.2

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Temp
    • Status: Closed
    • Critical
    • Resolution: Not A Problem
    • 2.0.14
    • None
    • Expression Language
    • None
    • Operating System: SUN
      Server: Weblogic 10.3
      Java: 1.6.0_5
      Current Struts: 1.2

    • Important

    Description

      Hi,
      We are in the process to upgrade our application. Currently our aplication is on
      Weblogic: 8.1sp5
      Java: 1.4
      Struts: 1.2

      We are upgrading it to:
      Server: Weblogic 10.3
      Java: 1.6.0_5
      Current Struts: 2.0.14
      We are facing issue with jsp expression in struts tag.
      All the expression which uses JSP variable as <%=name%> are not working and getting error "Request time value is not supported".
      As the application is old and there are lots of pages, this will take lot of time and effort to convert JSP expression to , i just want to know if there is any solution for this problem or we strictly need to use OGNL expression and change all JSPs.
      Is there any possibility that we can use JSP expression with struts 2.0.14, if not then which is the highest version supported for JSP expression.
      I tried with Struts 2.0.8 as mentioned in http://struts.apache.org/2.0.14/docs/why-cant-i-use-jstl-style-el-expressions-in-struts-tags.html link but it is also giving the same error.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            ashish_shr Ashish Shrivastava
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment