• Login
Community
  • Login

Validate Now, not able to validate XML against schema

Scheduled Pinned Locked Moved Help wanted · · · – – – · · ·
3 Posts 2 Posters 7.8k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    AngieBee
    last edited by AngieBee Sep 20, 2018, 3:23 PM Sep 20, 2018, 3:23 PM

    I have installed XML Tools and when I go to Plugins, Validate Now I get "Following error occurred during schema file parsing: Failed to locate the main schema resource 'ShowRepairOrder.xsd;. According to everything that I have read it should pop-up a box where I can select the schema .xsd file to compare the xml to, but I am not getting that. I have removed the XML Tools and reinstalled and I am still having the same issues. Can anyone help me with this?

    1 Reply Last reply Reply Quote 0
    • P
      PeterJones
      last edited by guy038 Feb 25, 2020, 2:02 PM Sep 20, 2018, 5:05 PM

      You might want to see if my reply in Need to load XSD helps, because it sounds similar to those events.

      Specifically, I think my conclusion that I drew from those experiments, “…that XML Tools will only ask you for the schema location if it’s not embedded in the XML itself; if it is embedded, it will automatically use the one it finds”, applies to your situation as well. It’s not prompting you because you specify it; it doesn’t seem to know that if it cannot find the specified one, it should also prompt.

      I believe that when it doesn’t find the specified, it should prompt for location, rather than just giving an error, so I have added a bug report to what appears to be the GitHub home for the XML Tools plugin: issue #11

      Update Feb 25, 2020: issue #11 has been closed; the problem is fixed as of XML Tools v3.0.3.2

      1 Reply Last reply Reply Quote 1
      • A
        AngieBee
        last edited by Sep 21, 2018, 12:54 AM

        Thanks for the reply. I ended up figuring it out after talking to a co-worker that uses XML Spy. I put the XML and .xsd files in the same folder and it validated. We then found the issue with the file.

        1 Reply Last reply Reply Quote 1
        2 out of 3
        • First post
          2/3
          Last post
        The Community of users of the Notepad++ text editor.
        Powered by NodeBB | Contributors