Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3351738
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T01:56:42+00:00 2026-05-18T01:56:42+00:00

I have an XML schema that was built with an old version of the

  • 0

I have an XML schema that was built with an old version of the XML spec (http://www.w3.org/1999/XMLSchema). I am trying to parse XML messages using the schema (shown below). By default, the Xerces 1.1 parser looks for the schema in the app domain root directory. I am trying to move the schema to a public location in our web directory. It seems like I cannot specify a URL as the schema location in my parsing program using the Xerces 1.1 library.

So I tried to upgrade my program to use JAXP DocumentBuilderFactory and its setSchema() method. This seems to find the schema with the schema URL I provide it, except that it gives parsing errors because the schema (presumably) does not conform to a later version of the spec (for example, I get errors because my Ticket element doesn’t wrap its members inside an xs:Sequence).

I can’t upgrade my schema since I can’t, at this time, force external customers to rewrite their apps that send messages to us.

Can anyone tell me how to use JAXP to successfully parse/validate using an old-school version of the schema spec? Or alternatively, is there a way to tell the Xerces 1.1 DOMParser to use a schema defined by a URL (not a file location)?

Here is a sample of what the schema looks like:

<?xml version="1.0" encoding="UTF-8" ?>
<schema>
  <element name="Ticket">
     <complexType>
        <element ref="ID" />
        <element ref="User" />
     </complexType>
  </element>

  <element name="ID" type='string' />
  <element name="UserID" type='string' />
</schema>

The XML document looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<Ticket xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
   xsi:noNamespaceSchemaLocation='TicketSubmission.xsd'>
  <ID>2010:December2:Dec:12:05:33:245</ID> 
  <UserID>user123</UserID> 
</Ticket>

Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T01:56:42+00:00Added an answer on May 18, 2026 at 1:56 am

    So, I’ve come to the conclusion that using the 1999 schema spec is a bad idea. Earlier versions of the Xerces parser that support the 1999 schema spec don’t seem to be flexible in where the schemas can reside on disk. I’m probably stuck with placing the schemas in the app server root directory until we can get our clients to use a newer version of our schema.

    Later versions of Xerces (even prior to Xerces 2) seem to have abandoned support of the 1999 schema spec in favor of the 2001 schema spec. Although, later versions of Xerces seem like they allow more flexibilty in the location of the schema files.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an XML Schema that I'm trying to create C# classes with. At
I have an XML schema that includes multiple addresses: <xs:element name=personal_address maxOccurs=1> <!-- address
I have a XML schema that I will need to create Java classes for.
I have an XML schema that represents a product in a DB, and I
I have a custom XML schema defined for page display that puts elements on
I have a xml blob that's checked against a schema in sql 2005. My
I have an xml message that is in the older schema (xsd) format. My
I have to make a schema for an XML format that's already being used.
I have a schema (xsd), and I want to create xml files that conform
I have an existing XML schema that contains a type that I would like

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.