Loading ...
Sorry, an error occurred while loading the content.

RE: [soapbuilders] Unknown attributes for WSDL

Expand Messages
  • Kirill Gavrylyuk
    We re fixing the issue at hand. But I agree with Glenn, that the restriction on wsdl:binding attribute extensibility was not the intent of WSDL spec and it
    Message 1 of 6 , Aug 5, 2005
    • 0 Attachment

      We’re fixing the issue at hand. But I agree with Glenn, that the restriction on wsdl:binding attribute extensibility was not the intent of WSDL spec and it would be ideal if WSDL4J allow attributes on wsdl:binding.

       


      From: soapbuilders@yahoogroups.com [mailto:soapbuilders@yahoogroups.com] On Behalf Of Sonali Kanaujia
      Sent: Friday, August 05, 2005 11:45 AM
      To: soapbuilders@yahoogroups.com
      Subject: Re: [soapbuilders] Unknown attributes for WSDL

       

      FYI--These are the Microsoft public RM endpoints that contain the non-compliant WSDLs. Look for wsp:PolicyURIs attribute on wsdl:binding. 

       

      -Sonali


      Glen Daniels <webservicedude@...> wrote:


      [cc'ed to soapbuilders because I think that community is generally
      interested in this kind of issue]

      Hi folks!

      In http://groups.yahoo.com/group/jsr110-eg-disc/message/687, dims notes
      that the schema for wsdl:binding doesn't support attribute extensions.
      However, Microsoft seems to have software out there which is generating
      such attributes - even if they fix this (as I believe they already have
      internally), there are still some WSDLs that have been released "into
      the wild" with this issue.

      WSDL4J currently will toss an exception if it encounters attributes
      where the schema doesn't allow them.  While in general I think faulting
      is correct behavior for this sort of thing, the fact is that we'd also
      like to enable interoperability as much as possible, and so some folks
      might want the ability to be a little more lenient with respect to
      "extra" content.

      What do you think of adding an "ignoreUnknown" option to WSDL4J?  When
      switched on this option would disable faulting in cases where the parser
      finds unexpected content - instead it would simply ignore it.

      Thoughts?
      --Glen


      Start your day with Yahoo! - make it your home page

    Your message has been successfully submitted and would be delivered to recipients shortly.