CDI Specification Issues
  1. CDI Specification Issues
  2. CDI-135

Request parameter for terminating cid propagation

    Details

    • Type: Feature Request Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 1.0
    • Fix Version/s: 1.1.EDR
    • Component/s: Contexts
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      The specification says the conversation id of non-transient conversations should be automatically propagated, it would however be handy to be able to stop this propagation on a per-component basis. If the request token (e.g. named "nocid") would be present, CDI would interpret this as if no cid was found in the request. This would enable users to jump from non-transient to non-transient conversations in one step (e.g. by using a commandLink with a f:param named nocid and an action that would start a new non-transient conversation.

      A further enhancement could be that the parameter value could be "end" and CDI would terminate the propagated non-transient conversation instead of just abandoning it.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            George Gastaldi added a comment -

            What about a conversationPropagation parameter ? Possible values could be end, nest or join.

            Show
            George Gastaldi added a comment - What about a conversationPropagation parameter ? Possible values could be end, nest or join.
            Hide
            Nicklas Karlsson added a comment -

            if the functionality would be extended, the parameter should probably be renamed to something like that, yes. But I'm not sure if nest should be an option since the CDI spec itself doesn't acknowledge this concept.

            Show
            Nicklas Karlsson added a comment - if the functionality would be extended, the parameter should probably be renamed to something like that, yes. But I'm not sure if nest should be an option since the CDI spec itself doesn't acknowledge this concept.
            Hide
            George Gastaldi added a comment -

            I prefer having a parameter whose values could be extended later than having a parameter "nocid" that could be replaced on later specs.

            Since put this way, the only possible values for this parameter is "end".

            Show
            George Gastaldi added a comment - I prefer having a parameter whose values could be extended later than having a parameter "nocid" that could be replaced on later specs. Since put this way, the only possible values for this parameter is "end".
            Hide
            Pete Muir added a comment -

            I agree, a conversationPropagation parameter seems more sensible.

            Show
            Pete Muir added a comment - I agree, a conversationPropagation parameter seems more sensible.
            Hide
            Pete Muir added a comment -

            See pull request. I only implemented the none propagation for now, as this is actually a hole in the spec, and not new functionality. I believe it would be possible to implement other propagations as an extension (George/Nickarls, could you verify this if you get 30 minutes sometime spare?).

            Show
            Pete Muir added a comment - See pull request. I only implemented the none propagation for now, as this is actually a hole in the spec, and not new functionality. I believe it would be possible to implement other propagations as an extension (George/Nickarls, could you verify this if you get 30 minutes sometime spare?).

              People

              • Assignee:
                Pete Muir
                Reporter:
                Nicklas Karlsson
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development