ICEfaces
  1. ICEfaces
  2. ICE-7433

Allow to disable automatic Ajax

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: EE-2.0.0.GA
    • Fix Version/s: None
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      -

      Description

      It would be very helpful for narrowing down problems if we could disable ICEfaces' automatic Ajax behaviour.

      We've found a couple of bugs which we're related especially in disabling Ajax where needed and we would rather like to chose ourselves if we want automatic Ajax behaviour or not. A web.xml Parameter would be fine.

        Activity

        Adrian Gygax created issue -
        Ted Goddard made changes -
        Field Original Value New Value
        Assignee Ted Goddard [ ted.goddard ]
        Hide
        Ted Goddard added a comment -

        It may be difficult to decouple some of the ICEfaces features: currently <icecore:config render="false"> allows you to turn off ICEfaces for a given page.
        Does the desired feature have D2D rendering enabled but ICEfaces event capture disabled? Certain ICEfaces components (such as compat components) cannot render without ICEfaces D2D active for the page.

        Show
        Ted Goddard added a comment - It may be difficult to decouple some of the ICEfaces features: currently <icecore:config render="false"> allows you to turn off ICEfaces for a given page. Does the desired feature have D2D rendering enabled but ICEfaces event capture disabled? Certain ICEfaces components (such as compat components) cannot render without ICEfaces D2D active for the page.
        Tyler Johnson made changes -
        Salesforce Case [5007000000JN2eO]
        Hide
        Adrian Gygax added a comment -

        It's only about the ICEfaces event capture. Due to ICE-7312 every ICEfaces 2.0 application (using JSF navigation) currently has pages without automatic Ajax by accident and because nobody (including us) noticed it outside of a portal environment it doesn't seem to be absolutely necessary.

        <icecore:config render="false"> is not an option because then <ice> as well as <ace> components don't work anymore or not correctly.

        Show
        Adrian Gygax added a comment - It's only about the ICEfaces event capture. Due to ICE-7312 every ICEfaces 2.0 application (using JSF navigation) currently has pages without automatic Ajax by accident and because nobody (including us) noticed it outside of a portal environment it doesn't seem to be absolutely necessary. <icecore:config render="false"> is not an option because then <ice> as well as <ace> components don't work anymore or not correctly.
        Hide
        Ted Goddard added a comment -

        If the form element contains the attribute DISABLE_CAPTURE_SUBMIT then the automatic Ajax capturing function ice.captureSubmit() is not written. This should disable automatic event capture.

        <h:form >
        <f:attribute name="DISABLE_CAPTURE_SUBMIT" value="true" />

        or

        <h:form >
        <f:ajax disabled="true" />

        Should both have the same effect. However, the <f:attribute> technique may be preferable since the <f:ajax> technique could have side effects within JSF itself.

        (I have not tested this recently, but it should be a useful debugging technique.)

        Show
        Ted Goddard added a comment - If the form element contains the attribute DISABLE_CAPTURE_SUBMIT then the automatic Ajax capturing function ice.captureSubmit() is not written. This should disable automatic event capture. <h:form > <f:attribute name="DISABLE_CAPTURE_SUBMIT" value="true" /> or <h:form > <f:ajax disabled="true" /> Should both have the same effect. However, the <f:attribute> technique may be preferable since the <f:ajax> technique could have side effects within JSF itself. (I have not tested this recently, but it should be a useful debugging technique.)
        Hide
        Adrian Gygax added a comment -

        Hi Ted

        Thanks a lot!

        <f:attribute name="DISABLE_CAPTURE_SUBMIT" value="true" /> works and does what we need for debugging purposes.

        Cheers
        Adrian

        Show
        Adrian Gygax added a comment - Hi Ted Thanks a lot! <f:attribute name="DISABLE_CAPTURE_SUBMIT" value="true" /> works and does what we need for debugging purposes. Cheers Adrian
        Ken Fyten made changes -
        Assignee Ted Goddard [ ted.goddard ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Adrian Gygax
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: