Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Component/s: Ajax/JavaScript
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      879
    • Status Whiteboard:
      Hide

      size_large importance_large draft

      Show
      size_large importance_large draft

      Description

      I suggest to introduce concept of decoders as functionality that works
      independently from rendering functionality. JSF already has dedicated Renderer
      class. So it makes sense to do the same thing for decoding functionality.
      The first benefit from this approach would be possibility to send data from
      client directly to decoder, skipping on the way to it necessity to use JSF
      components and JSF life cycle. JSF developers will be able to create more
      stateless JSF applications and use Javascript libraries in more flexible than
      now manner.

      The first usage of decoder would be the following kind of scenario:

      client side:
      jsf.ajax.post({data:

      {'dataHolder.value': value1}

      , render: 'input1');

      server side:
      if (isDataRequest(context.getExternalContext().getRequestHeaderMap()))

      { Decoder.handleDataRequest(context); context.responseComplete(); }

      ...
      ValueExpression ve = getValueExpression(context, key);
      ve.setValue(context.getELContext(), o.get(key));
      ...

      Note: The first argument of the method "post" would be optional and called "url".
      In case if developer need to customize handling of data from client we will use
      this argument as way to identify decoder that will handle the data.

      Complete signature of the Javascript method could be defined something like this:
      jsf.ajax.post([url], [data], [handleAs], [render], [onSuccess(data)],
      onError(data)]);

        Activity

        Hide
        vladperl added a comment -

        The following link seems could be used as supporting point:
        http://forums.java.net/jive/thread.jspa?messageID=481227

        Show
        vladperl added a comment - The following link seems could be used as supporting point: http://forums.java.net/jive/thread.jspa?messageID=481227
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            vladperl
          • Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: