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

10285Re: [soapbuilders] Re: .Net is automatically importing XML schema, how do I stop it from doing so??

Expand Messages
  • Anne Thomas Manes
    Jun 2, 2005
    • 0 Attachment
      And FYI, the location of the xsd schema is http://www.w3.org/2001/XMLSchema.xsd.

      On 6/2/05, Kirill Gavrylyuk <kirillg@...> wrote:
      > >.Net didn't specify a
      > >location and according to what I've read you need to use the
      > >"schemaLocation" attribute when importing an XML schema into your WSDL
      > >document and need to use the xsd:import and not the wsdl:import.
      >
      > BP does not require schemaLocation for xsd:import
      > BP requires location attribute for wsdl:import.
      >
      > The failure you see seems like a bug in WS-I test tools (does not
      > recognize a known schema and fails to test the other requirement).
      >
      > >-----Original Message-----
      > >From: soapbuilders@yahoogroups.com
      > [mailto:soapbuilders@yahoogroups.com] On
      > >Behalf Of rjc7878
      > >Sent: Thursday, June 02, 2005 8:56 AM
      > >To: soapbuilders@yahoogroups.com
      > >Subject: [soapbuilders] Re: .Net is automatically importing XML schema,
      > how
      > >do I stop it from doing so??
      > >
      > >The WS-I profile doesn't prohibit importing sorry about that. They
      > >just specify a certain way it needs to be done. .Net didn't specify a
      > >location and according to what I've read you need to use the
      > >"schemaLocation" attribute when importing an XML schema into your WSDL
      > >document and need to use the xsd:import and not the wsdl:import.
      > >
      > >The following is the message I get from the WS-I tools:
      > >
      > >Failure on WSI2102
      > >An XML schema import element references something other than an XML
      > >schema definition: the referenced element does not have "schema" from
      > >XML namespace "http://www.w3.org/2001/XMLSchema" as root element.
      > >
      > >However, thanks for poiting out the use of DataSet. Another developer
      > >added this for .Net clients and I'm working on separating it out to a
      > >separate interface so I have one that provides a more interoperable
      > >interface for other clients. When I removed the dataset the import
      > >went away and solved my issue. Thanks much!
      > >
      > >Ryan
      > >
      > >
      > >--- In soapbuilders@yahoogroups.com, Anne Thomas Manes <atmanes@g...>
      > >wrote:
      > >> I just scanned through the WS-I Basic Profile and could find no
      > >> prohibition about importing the xsd namespace, so I don't believe
      > it's
      > >> invalid. As Kirill says, it's most likely caused by the fact that
      > your
      > >> interface includes a DataSet, which includes an embedded schema.
      > >>
      > >> Although DataSet isn't prohibited by the WS-I BP, it does cause
      > >> significant interop problems and therefore should be avoided.
      > >>
      > >> Anne
      > >>
      > >> On 6/2/05, Kirill Gavrylyuk <kirillg@m...> wrote:
      > >> > Hi Ryan,
      > >> >
      > >> > >>This import is not allowed by the WS-I basic profile
      > >> > I assume prefix "s" in this case refers to the
      > >> > "http://www.w3.org/2001/XMLSchema" namespace uri and import is
      > located
      > >> > inside the <s:schema> element?
      > >> >
      > >> > If true, why is it invalid?
      > >> >
      > >> > Anyway, this is most likely there because you're using DataSet.
      > >> >
      > >> >
      > >> > >-----Original Message-----
      > >> > >From: soapbuilders@yahoogroups.com
      > >> > [mailto:soapbuilders@yahoogroups.com] On
      > >> > >Behalf Of rjc7878
      > >> > >Sent: Wednesday, June 01, 2005 8:27 PM
      > >> > >To: soapbuilders@yahoogroups.com
      > >> > >Subject: [soapbuilders] .Net is automatically importing XML
      > >schema, how
      > >> > do
      > >> > >I stop it from doing so???
      > >> > >
      > >> > >All,
      > >> > >
      > >> > >The WSDL that my .Net Web Service is generating contains the
      > >> > >following
      > >> > >statement:
      > >> > >
      > >> > ><s:import namespace="http://www.w3.org/2001/XMLSchema"/>
      > >> > >
      > >> > >This import is not allowed by the WS-I basic profile and thus I'm
      > >> > >trying to
      > >> > >remove it. I haven't been able to find what is causing this to be
      > >> > >added to
      > >> > >my WSDL or which attribute I can add to prevent it from being
      > >> > >added. Can
      > >> > >anyone tell me why this is getting put into the WSDL file. This
      > >> > >schema
      > >> > >should not need to be imported in the first place.
      > >> > >
      > >> > >Thanks,
      > >> > >Ryan
      > >> > >
      > >> > >
      > >> > >
      > >> > >
      > >> > >
      > >> > >-----------------------------------------------------------------
      > >> > >This group is a forum for builders of SOAP implementations to
      > discuss
      > >> > >implementation and interoperability issues. Please stay on-topic.
      > >> > >Yahoo! Groups Links
      > >> > >
      > >> > >
      > >> > >
      > >> > >
      > >> > >
      > >> > >
      > >> >
      > >> >
      > >> >
      > >> > -----------------------------------------------------------------
      > >> > This group is a forum for builders of SOAP implementations to
      > >discuss implementation and interoperability issues. Please stay
      > on-topic.
      > >> > Yahoo! Groups Links
      > >> >
      > >> >
      > >> >
      > >> >
      > >> >
      > >> >
      > >> >
      > >
      > >
      > >
      > >
      > >-----------------------------------------------------------------
      > >This group is a forum for builders of SOAP implementations to discuss
      > >implementation and interoperability issues. Please stay on-topic.
      > >Yahoo! Groups Links
      > >
      > >
      > >
      > >
      > >
      > >
      >
      >
      >
      > -----------------------------------------------------------------
      > This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues. Please stay on-topic.
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
      >
      >
    • Show all 8 messages in this topic