ICEfaces
  1. ICEfaces
  2. ICE-1512

Seam page parameters are being kept as List of Strings rather than String

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6DR#3
    • Fix Version/s: 1.6DR#4, 1.6
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      all
    • Workaround Description:
      currently trying to find one for seam-gen

      Description

      in the *.page.xml files, the parameters that are not bound to a value in a bean are being stored as List of Strings. They are used in redirect using EL in seam-gen for example the following expression:-
             <s:link view="/#{empty from ? 'Contactentry' : from}.xhtml"

      This results in a redirect like the following:-
      http://localhost:8080/ice3/%5BLjava.lang.String;@1c8ce14.seam?contactgroupContactGroupId=1&cid=10

        Issue Links

          Activity

          Hide
          Judy Guglielmin added a comment -

          Standard Request Scope (context parameter) takes care of this.

          Show
          Judy Guglielmin added a comment - Standard Request Scope (context parameter) takes care of this.
          Hide
          Eduardo Nieto added a comment -

          i have the same problem in my apps. especially when working with many-to-many relationships.

          anyone found a workaround?

          Show
          Eduardo Nieto added a comment - i have the same problem in my apps. especially when working with many-to-many relationships. anyone found a workaround?
          Hide
          Judy Guglielmin added a comment -

          put the following in your web.xml to have the parameters returned as string

          <context-param>
          <param-name>com.icesoft.faces.standardRequestScope</param-name>
          <param-value>true</param-value>
          </context-param>

          Show
          Judy Guglielmin added a comment - put the following in your web.xml to have the parameters returned as string <context-param> <param-name>com.icesoft.faces.standardRequestScope</param-name> <param-value>true</param-value> </context-param>
          Hide
          Eduardo Nieto added a comment -

          ty very much! that was a fast reply!!

          by the way... don't you think seam-gen should set Standard Request Scope true by default???

          thx again... bye

          Show
          Eduardo Nieto added a comment - ty very much! that was a fast reply!! by the way... don't you think seam-gen should set Standard Request Scope true by default??? thx again... bye
          Hide
          Judy Guglielmin added a comment -

          If you only knew how many variations of things we have done lately! Both Seam and Icefaces are releasing new versions pretty quickly, but we'll keep that in mind.

          Show
          Judy Guglielmin added a comment - If you only knew how many variations of things we have done lately! Both Seam and Icefaces are releasing new versions pretty quickly, but we'll keep that in mind.
          Hide
          Eduardo Nieto added a comment -

          i tried using standard request scope, but now all the rest of my app doesnt work =(.. i guess it stops ajax request from being sent...

          i guess your work its pretty overwhelming...=S, just keep the good work and thanks for helping

          Show
          Eduardo Nieto added a comment - i tried using standard request scope, but now all the rest of my app doesnt work =(.. i guess it stops ajax request from being sent... i guess your work its pretty overwhelming...=S, just keep the good work and thanks for helping
          Hide
          Judy Guglielmin added a comment -

          Actually that's not true. If you look at our seam-component-showcase, you can see the standard request scope is working and it uses the ajax calls all the time. You might want to check your configuration files with those. Maybe you don't have the RenderManager setup in application scope (you have to do this in the components.xml).....definitely check out all the xml files (web.xml, faces-config, components.xml )to ensure you are setting the project up properly.

          Show
          Judy Guglielmin added a comment - Actually that's not true. If you look at our seam-component-showcase, you can see the standard request scope is working and it uses the ajax calls all the time. You might want to check your configuration files with those. Maybe you don't have the RenderManager setup in application scope (you have to do this in the components.xml).....definitely check out all the xml files (web.xml, faces-config, components.xml )to ensure you are setting the project up properly.
          Hide
          Judy Guglielmin added a comment -

          has been fixed with standard request scope

          Show
          Judy Guglielmin added a comment - has been fixed with standard request scope
          Hide
          Eduardo Nieto added a comment -

          i have the default config that you get when using seam-gen and still having the same problem.

          i think i have the render manager properlly set.

          is this issue solved in DR4??? Maybe all i have to do is upgrade =P

          Show
          Eduardo Nieto added a comment - i have the default config that you get when using seam-gen and still having the same problem. i think i have the render manager properlly set. is this issue solved in DR4??? Maybe all i have to do is upgrade =P
          Hide
          Judy Guglielmin added a comment -

          sorry...I had assumed that you had already upgraded to DR4. Yeah...you want DR4 as well as Seam1.2.1.GA and use the configuration files from seam-component-showcase or a project that you generate from icefaces-seam-gen

          Show
          Judy Guglielmin added a comment - sorry...I had assumed that you had already upgraded to DR4. Yeah...you want DR4 as well as Seam1.2.1.GA and use the configuration files from seam-component-showcase or a project that you generate from icefaces-seam-gen
          Hide
          Eduardo Nieto added a comment -

          you were right... DR4 did the magic...

          thx a lot... looking forward to bother you with other issue...xD

          Show
          Eduardo Nieto added a comment - you were right... DR4 did the magic... thx a lot... looking forward to bother you with other issue...xD
          Hide
          Judy Guglielmin added a comment -

          No problem, that's what we're here for...

          Show
          Judy Guglielmin added a comment - No problem, that's what we're here for...

            People

            • Assignee:
              Unassigned
              Reporter:
              Judy Guglielmin
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: