Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » XML Schema Definition (XSD) » Schema has not been resolved
Schema has not been resolved [message #46178] Thu, 27 May 2004 07:54 Go to next message
Eclipse User
Originally posted by: invalid.soft-gems.net

Hi all,

I've got a problem when I moved my schemas from local harddisk to a web
server. There is this root schema (imported via an absolute path), which
includes 3 other schemas (which in turn import yet a couple of other
schemas). All the schemas are located in the same folder on the web server
(an IBM AIX machine with Apache). This works mostly well and fine except
for one schema, which does not get loaded. It is one of the schemas
imported by the root schema and I can't for my life find any reason for
the failing load. Using Internet Explorer or XML Spy the schema can be
accessed without problems. I checked exact spelling at least half a dozen
times as well as the user rights. The schema itself is not yet used, just
imported, but did not produce any error message when it was stored
locally, so I assume this is not the reason for the problem.

Any useful hint would be much appreciated.

Mike
--
www.soft-gems.net
Re: Schema has not been resolved [message #46238 is a reply to message #46178] Thu, 27 May 2004 10:17 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

--------------1E31CD7086335D0070BBEE9D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike,

Imported schemas are loaded on demand when the first name lookup requires it
to be resolved in order to search that namespace for the name. If the schema
isn't used, it won't be imported.

In the XSDEcoreBuilder, in order to force the lookups to happen, I used the
following:

for (Iterator i = xsdSchema.getContents().iterator(); i.hasNext(); )

{
Object content = i.next();
if (content instanceof XSDImport)
{
XSDImport xsdImport = (XSDImport)content;
xsdImport.resolveTypeDefinition(xsdImport.getNamespace(), "");
}
}

(Note that because of substitution groups, it's possible that resolving an
import can cause the importing schema to become invalid by virtue of the
substitution group contributions of the imported schema.)


Mike Lischke wrote:

> Hi all,
>
> I've got a problem when I moved my schemas from local harddisk to a web
> server. There is this root schema (imported via an absolute path), which
> includes 3 other schemas (which in turn import yet a couple of other
> schemas). All the schemas are located in the same folder on the web server
> (an IBM AIX machine with Apache). This works mostly well and fine except
> for one schema, which does not get loaded. It is one of the schemas
> imported by the root schema and I can't for my life find any reason for
> the failing load. Using Internet Explorer or XML Spy the schema can be
> accessed without problems. I checked exact spelling at least half a dozen
> times as well as the user rights. The schema itself is not yet used, just
> imported, but did not produce any error message when it was stored
> locally, so I assume this is not the reason for the problem.
>
> Any useful hint would be much appreciated.
>
> Mike
> --
> www.soft-gems.net

--------------1E31CD7086335D0070BBEE9D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Mike,
<p>Imported schemas are loaded on demand when the first name lookup requires
it to be resolved in order to search that namespace for the name.&nbsp;
If the schema isn't used, it won't be imported.
<p>In the XSDEcoreBuilder, in order to force the lookups to happen, I used
the following:
<blockquote>for (Iterator i = xsdSchema.getContents().iterator(); i.hasNext();
)
<br>{
<br>&nbsp; Object content = i.next();
<br>&nbsp; if (content instanceof XSDImport)
<br>&nbsp; {
<br>&nbsp;&nbsp;&nbsp; XSDImport xsdImport = (XSDImport)content;
<br>&nbsp;&nbsp;&nbsp; xsdImport.resolveTypeDefinition(xsdImport.getNamespace(),
"");
<br>&nbsp; }
<br>}</blockquote>
(Note that because of substitution groups, it's possible that resolving
an import can cause the importing schema to become invalid by virtue of
the substitution group contributions of the imported schema.)
<br>&nbsp;
<p>Mike Lischke wrote:
<blockquote TYPE=CITE>Hi all,
<p>I've got a problem when I moved my schemas from local harddisk to a
web
<br>server. There is this root schema (imported via an absolute path),
which
<br>includes 3 other schemas (which in turn import yet a couple of other
<br>schemas). All the schemas are located in the same folder on the web
server
<br>(an IBM AIX machine with Apache). This works mostly well and fine except
<br>for one schema, which does not get loaded. It is one of the schemas
<br>imported by the root schema and I can't for my life find any reason
for
<br>the failing load. Using Internet Explorer or XML Spy the schema can
be
<br>accessed without problems. I checked exact spelling at least half a
dozen
<br>times as well as the user rights. The schema itself is not yet used,
just
<br>imported, but did not produce any error message when it was stored
<br>locally, so I assume this is not the reason for the problem.
<p>Any useful hint would be much appreciated.
<p>Mike
<br>--
<br>www.soft-gems.net</blockquote>
</html>

--------------1E31CD7086335D0070BBEE9D--
Re: Schema has not been resolved [message #46265 is a reply to message #46238] Thu, 27 May 2004 11:07 Go to previous message
Eclipse User
Originally posted by: invalid.soft-gems.net

Ed Merks wrote:

> Imported schemas are loaded on demand when the first name lookup requires it
> to be resolved in order to search that namespace for the name. If the schema
> isn't used, it won't be imported.

Thank you for that tip Ed. I only wonder why I didn't get a warning when I
had the schemas on my local harddisk, but this may have a total unrelated
reason.

Mike
--
www.soft-gems.net
Re: Schema has not been resolved [message #587762 is a reply to message #46178] Thu, 27 May 2004 10:17 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26141
Registered: July 2009
Senior Member
--------------1E31CD7086335D0070BBEE9D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mike,

Imported schemas are loaded on demand when the first name lookup requires it
to be resolved in order to search that namespace for the name. If the schema
isn't used, it won't be imported.

In the XSDEcoreBuilder, in order to force the lookups to happen, I used the
following:

for (Iterator i = xsdSchema.getContents().iterator(); i.hasNext(); )

{
Object content = i.next();
if (content instanceof XSDImport)
{
XSDImport xsdImport = (XSDImport)content;
xsdImport.resolveTypeDefinition(xsdImport.getNamespace(), "");
}
}

(Note that because of substitution groups, it's possible that resolving an
import can cause the importing schema to become invalid by virtue of the
substitution group contributions of the imported schema.)


Mike Lischke wrote:

> Hi all,
>
> I've got a problem when I moved my schemas from local harddisk to a web
> server. There is this root schema (imported via an absolute path), which
> includes 3 other schemas (which in turn import yet a couple of other
> schemas). All the schemas are located in the same folder on the web server
> (an IBM AIX machine with Apache). This works mostly well and fine except
> for one schema, which does not get loaded. It is one of the schemas
> imported by the root schema and I can't for my life find any reason for
> the failing load. Using Internet Explorer or XML Spy the schema can be
> accessed without problems. I checked exact spelling at least half a dozen
> times as well as the user rights. The schema itself is not yet used, just
> imported, but did not produce any error message when it was stored
> locally, so I assume this is not the reason for the problem.
>
> Any useful hint would be much appreciated.
>
> Mike
> --
> www.soft-gems.net

--------------1E31CD7086335D0070BBEE9D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Mike,
<p>Imported schemas are loaded on demand when the first name lookup requires
it to be resolved in order to search that namespace for the name.&nbsp;
If the schema isn't used, it won't be imported.
<p>In the XSDEcoreBuilder, in order to force the lookups to happen, I used
the following:
<blockquote>for (Iterator i = xsdSchema.getContents().iterator(); i.hasNext();
)
<br>{
<br>&nbsp; Object content = i.next();
<br>&nbsp; if (content instanceof XSDImport)
<br>&nbsp; {
<br>&nbsp;&nbsp;&nbsp; XSDImport xsdImport = (XSDImport)content;
<br>&nbsp;&nbsp;&nbsp; xsdImport.resolveTypeDefinition(xsdImport.getNamespace(),
"");
<br>&nbsp; }
<br>}</blockquote>
(Note that because of substitution groups, it's possible that resolving
an import can cause the importing schema to become invalid by virtue of
the substitution group contributions of the imported schema.)
<br>&nbsp;
<p>Mike Lischke wrote:
<blockquote TYPE=CITE>Hi all,
<p>I've got a problem when I moved my schemas from local harddisk to a
web
<br>server. There is this root schema (imported via an absolute path),
which
<br>includes 3 other schemas (which in turn import yet a couple of other
<br>schemas). All the schemas are located in the same folder on the web
server
<br>(an IBM AIX machine with Apache). This works mostly well and fine except
<br>for one schema, which does not get loaded. It is one of the schemas
<br>imported by the root schema and I can't for my life find any reason
for
<br>the failing load. Using Internet Explorer or XML Spy the schema can
be
<br>accessed without problems. I checked exact spelling at least half a
dozen
<br>times as well as the user rights. The schema itself is not yet used,
just
<br>imported, but did not produce any error message when it was stored
<br>locally, so I assume this is not the reason for the problem.
<p>Any useful hint would be much appreciated.
<p>Mike
<br>--
<br>www.soft-gems.net</blockquote>
</html>

--------------1E31CD7086335D0070BBEE9D--
Re: Schema has not been resolved [message #587776 is a reply to message #46238] Thu, 27 May 2004 11:07 Go to previous message
Mike Lischke is currently offline Mike Lischke
Messages: 78
Registered: July 2009
Member
Ed Merks wrote:

> Imported schemas are loaded on demand when the first name lookup requires it
> to be resolved in order to search that namespace for the name. If the schema
> isn't used, it won't be imported.

Thank you for that tip Ed. I only wonder why I didn't get a warning when I
had the schemas on my local harddisk, but this may have a total unrelated
reason.

Mike
--
www.soft-gems.net
Previous Topic:Schema has not been resolved
Next Topic:BaseType of a underived ComplexType
Goto Forum:
  


Current Time: Sat Oct 25 08:47:44 GMT 2014

Powered by FUDForum. Page generated in 0.02941 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software