Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-1068

Cannot handle xsd:import of xml schema

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jbossws-1.0.2
    • None
    • jbossws-native
    • None

      <!--TODO Parser complains about this
      xs:import namespace="http://www.w3.org/XML/1998/namespace"
      schemaLocation="http://www.w3.org/2001/xml.xsd"/-->

      Chris sais:

      On Jul 10, 2006, at 7:14 PM, Julien Viet wrote:

      > This is a general xml schema issue. Is the namespace URI not correctly registered with the JBossEntityResolver?

      Note that the URI causing problem is the standard XML schema address (http://www.w3.org/2001/xml.xsd). I would assume that this schema would be bundled with the WS stack and resolved to the local version at runtime to avoid remote access. Not only this, but even when you have an internet connection available but are behind a firewall/proxy, the XML parser can also fail to retrieve the remote schema...

      How do I check what is known by JBossEntityResolver? How do I configure it?

      > In case it is not, there is no known workaround. Entity resolution will be handeled by OASIS catalog support in future

      What's the timeline on this? Is catalog a standard now? Last time I looked at it (in my previous job), it didn't seem finished/adopted...

        1. wsrp_services.wsdl
          1 kB
        2. wsrp_v1_bindings.wsdl
          16 kB
        3. wsrp_v1_interfaces.wsdl
          17 kB
        4. wsrp_v1_types.xsd
          34 kB

              tdiesler@redhat.com Thomas Diesler
              tdiesler@redhat.com Thomas Diesler
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: