Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-4739

Fix injection of seam components in reentrance cases

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1.0.GA, 2.2.0.GA, 2.2.1.CR2
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      In reentrance cases (same component called twice recursively for instance), the component is not injected/disinjected correctly, which can leave the component in an invalid state.

      This is due to a misplaced check on injection state of the component in BijectionInterceptor.java: instead of being performed in the finally block, it should be placed in the catch block.
      This is useful in case of unexpected errors (to let the component in a valid state) but also in case of expected errors (for instance when a method performs a JSF validation and throws a ValidatorException).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                atchertchian Anahide Tchertchian
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: