Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-3573

When a timer without graphelement fires, UserCodeInterceptorConfig.userCodeInterceptor is not called

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • jBPM 3.2.x
    • jBPM 3.2.5 GA
    • Runtime Engine
    • None

    • jbpm 3.2.5 GA
      jboss 4.2.3
      seam 2.1.2

      When a jbpm timer fires, and Timer.graphElement is null, it calls the action directly without going through the user code interceptor. This causes the processInstance component in seam to be null

              marco.rietveld Marco Rietveld (Inactive)
              mark_v_torres Mark Torres (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: