Uploaded image for project: 'Woden'
  1. Woden
  2. WODEN-17

When a binding doesn't specify an interface, Wodwn emits an invalid <interface ref="id-null"/> reference.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Parser
    • Labels:
      None

      Description

      This problem was described by Jonathan Marsh in a post to the W3C WSDL working group [1].

      When a binding doesn't specify an interface, Wodwn emits an invalid <interface ref="id-null"/> reference.

      John, sounds to me like this falls under the resposibility of the parser. Feel free to reassign if I'm incorrect.

      [1] http://lists.w3.org/Archives/Public/www-ws-desc/2006May/0074.html

        Activity

        Hide
        ryman Arthur Ryman added a comment -

        Closing.

        Show
        ryman Arthur Ryman added a comment - Closing.
        Hide
        jkaputin John Kaputin added a comment -

        Arthur, I think Lawrence opened this at your request. Can we close it now?

        Show
        jkaputin John Kaputin added a comment - Arthur, I think Lawrence opened this at your request. Can we close it now?
        Hide
        ryman Arthur Ryman added a comment -

        Done.

        Show
        ryman Arthur Ryman added a comment - Done.
        Hide
        ryman Arthur Ryman added a comment -

        I fixed the Ant task to check for OPTIONAL references.

        Show
        ryman Arthur Ryman added a comment - I fixed the Ant task to check for OPTIONAL references.
        Hide
        ryman Arthur Ryman added a comment -

        The parser is ok. It's the Ant task that is writing out the id-null. I'll correct this.

        Show
        ryman Arthur Ryman added a comment - The parser is ok. It's the Ant task that is writing out the id-null. I'll correct this.
        Hide
        jkaputin John Kaputin added a comment -

        Recall from previous discussions on model creation and validation that we agreed it is possible for Woden to create and return and invalid model. The validation errors get reported, but the invalid model still gets returned. This approach is necessary in WSDL editor use cases, where the WSDL is a work-in-progress that will eventually become valid.

        > When a binding doesn't specify an interface, Wodwn emits an invalid <interface ref="id-null"/> reference.

        Check to see if Woden validation is correctly reporting this error. It may be that the testing Jonathan is doing expects the parse to fail if an error is encountered (a.k.a WSDL4J), rather than an invalid model being returned along with validation errors.

        Show
        jkaputin John Kaputin added a comment - Recall from previous discussions on model creation and validation that we agreed it is possible for Woden to create and return and invalid model. The validation errors get reported, but the invalid model still gets returned. This approach is necessary in WSDL editor use cases, where the WSDL is a work-in-progress that will eventually become valid. > When a binding doesn't specify an interface, Wodwn emits an invalid <interface ref="id-null"/> reference. Check to see if Woden validation is correctly reporting this error. It may be that the testing Jonathan is doing expects the parse to fail if an error is encountered (a.k.a WSDL4J), rather than an invalid model being returned along with validation errors.
        Hide
        ryman Arthur Ryman added a comment -

        I'll investigate.

        Show
        ryman Arthur Ryman added a comment - I'll investigate.

          People

          • Assignee:
            ryman Arthur Ryman
            Reporter:
            lmandel Lawrence Mandel
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development