ODE
  1. ODE
  2. ODE-163

Parser/BOM can not handle all BPEL namespaces

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1
    • Labels:
      None

      Description

      e.g. when parsing/compiling a <wait xmlns="bpel2.0final"> statement, the parser expects a <for xmlns="bpel2.0draft"> spuriously.

        Activity

        Hide
        Tammo van Lessen added a comment -

        Yeah, makes sense. I changed it again - now such children are expected to be in the same namespace as the parent element. Others are treated as extension elements.

        Show
        Tammo van Lessen added a comment - Yeah, makes sense. I changed it again - now such children are expected to be in the same namespace as the parent element. Others are treated as extension elements.
        Tammo van Lessen committed 561946 (1 file)
        Hide
        Paul R. Brown added a comment -

        I would probably have voted for a warning in the compiler, since in schema validation terms the @BPEL2D namespace is technically an extension namespace in an @BPEL2F process document.

        Show
        Paul R. Brown added a comment - I would probably have voted for a warning in the compiler, since in schema validation terms the @BPEL2D namespace is technically an extension namespace in an @BPEL2F process document.
        Tammo van Lessen made changes -
        Field Original Value New Value
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.1 [ 12312471 ]
        Hide
        Tammo van Lessen added a comment -

        Fixed. I've chosen the robust solution, so a <for>@BPEL2F as well as @BPEL2D is allowed in a <wait>@BPEL2F.

        Fixed for wait, onAlarm, forEach and the event handler getter in Scopes.

        Show
        Tammo van Lessen added a comment - Fixed. I've chosen the robust solution, so a <for>@BPEL2F as well as @BPEL2D is allowed in a <wait>@BPEL2F. Fixed for wait, onAlarm, forEach and the event handler getter in Scopes.
        Tammo van Lessen created issue -

          People

          • Assignee:
            Tammo van Lessen
            Reporter:
            Tammo van Lessen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development