Details

      Description

      this scope should be similar to the conversation scope of orchestra.

      annotation: @ConversationScoped

      if no @ConversationGroup(MyGroup.class) is provided, the class of the bean is used as group.

      it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
      it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.

      it should be possible to create stereotypes.
      if a meta-annotation and the bean don't host a group, the class of the stereotype is used as conversation group.

        Activity

        Gerhard Petracek made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Gerhard Petracek made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Assignee Gerhard Petracek [ gpetracek ]
        Gerhard Petracek made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Gerhard Petracek made changes -
        Component/s JEE-JSF12-Module [ 12313496 ]
        Component/s JEE-JSF20-Module [ 12313497 ]
        Gerhard Petracek made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.0.0-SNAPSHOT [ 12314885 ]
        Resolution Fixed [ 1 ]
        Gerhard Petracek made changes -
        Summary named conversation scope (grouped) conversation scope
        Description this scope should be similar to the conversation scope of orchestra.

        annotation: @NamedConversation

        if no qualifier (meta-annotation) is provided, the class-name (decapitalized) is used as conversation name.

        it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
        it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.

        it should be possible to create stereotypes.
        if a meta-annotation provides no or an empty conversation name, the name of the stereotype is used as conversation name (instead of the name of the bean-class).

        this scope should be similar to the conversation scope of orchestra.

        annotation: @ConversationScoped

        if no @ConversationGroup(MyGroup.class) is provided, the class of the bean is used as group.

        it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
        it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.

        it should be possible to create stereotypes.
        if a meta-annotation and the bean don't host a group, the class of the stereotype is used as conversation group.

        Gerhard Petracek made changes -
        Field Original Value New Value
        Description this scope should be similar to the conversation scope of orchestra.

        annotation: @NamedConversation

        if no qualifier (meta-annotation) is provided, the class-name (decapitalized) is used as conversation name.

        it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
        it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.
        this scope should be similar to the conversation scope of orchestra.

        annotation: @NamedConversation

        if no qualifier (meta-annotation) is provided, the class-name (decapitalized) is used as conversation name.

        it should be allowed to use different conversations at the same time (one conversation for 1-n beans).
        it should be possible to invalidate and/or restart conversations immediately (not at the end of a request) and it should be independent of plain cdi-conversations. so users can use both concepts in parallel.

        it should be possible to create stereotypes.
        if a meta-annotation provides no or an empty conversation name, the name of the stereotype is used as conversation name (instead of the name of the bean-class).

        Gerhard Petracek created issue -

          People

          • Assignee:
            Gerhard Petracek
            Reporter:
            Gerhard Petracek
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development