Not able to access schema from a Web Server

Question

I am not successful in using a schema from a web server. I am using j2sdk1.4.2_06, and JDOM-b10. I have been successful in accessing schema using a file path, but not with a web address. The server is Windows Server 2003, I create a virtual directory using IIS under Inetpub.
Let the URL be: http://server/research_schema/client.xsd
This would be accessible only on the intranet.
Here is some XML:
<client xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:noNamespaceSchemaLocation="http://server/research_schema/client.xsd">
<execute matlab="false" commit="false" return_server_msg="false">
<t1>
<load_batch_data>
<username>test</username>
<password>test</password>
<database>db</database>
<get_next_batch>true</get_next_batch>
</load_batch_data>
</t1>
</execute>
</client>
  Here is the code that sets the parser to be validating, and sets the schema location, I am using JDOM:
builder = new SAXBuilder("org.apache.xerces.parsers.SAXParser", true);
builder.setFeature(
  "http://apache.org/xml/features/validation/schema",
  true);
builder.setProperty(
   "http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation",
        "http://server/research_schema/client.xsd");
doc = builder.build(source);The error I get is a JDOMException saying the client element is not found, but I know that the client element is there, after seeing the XML output to
a file from the sender.
I see many exmples on the internet using a URL for the schema location, and it is usually the internet and not just the intranet. So it does work for someone.
I'd appreaciate any help.

Answer 1

Steve, et. al.,
My apologies for using this in lieu of email, but I have been searching and searching for the answer to your questions from last summer concerning the correct method for getting the local xsd file to be correctly accessed from the xml file when using JDOM to parse with validation..
I did not see successful resolution of the thread from last summer, but this one seems closely related and suggests that you were either instructed to give up, or gave up on your own and went to the solution of placing the xsd file on a server.
Maybe I've got my head screwed on wrong, but I, like you, would like to find a successful way to make xml processing work for a JWS-provisioned application the same as it would if I just sent the clients a big jar file and told them to unjar it to some convenient local directory. In that scenario xsi:noNamespaceSchemaLocation = "itsrighthere.xsd" works as expected.
Can anyone tell us what the correct method of specification is in the JWS context?
Thank you.