Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
XMLSchemaLoader handling inlined schemas

XMLSchemaLoader handling inlined schemas

2004-03-03       - By Jeehong Min
Reply:     1     2  

I am trying to obtain XSModels for inlined schemas in WSDLs.

I am able to do this successfully, except when the inlined schemas reference
each other.  For instance, assume I have 2 inlined schemas in the WSDL.

<definitions>
<types>

<xsd:schema targetNamespace="foo" xmlns:xsd="...">
...
</schema>

<xsd:schema targetNamespace="bar" xmlns:xsd="...">
<xsd:import namespace="foo"/>
...
</schema>

</types>
</definition>

Some type declarations in "bar" schema reference elements in the "foo" schema.
As a result, when I try to load the schema for "bar" schema, I get an error
saying that it cannot resolve the name "nsBar:Something" when nsBar is the
prefix for "bar" namespace.

I am doing this:
loader is instance of XMLSchemaLoader
SchemaGrammer grammar = loader.loadGrammar(source) where source is the
XMLInputSource representing the inlined schema.
XSModel model = grammar.toXSModel()

I've tried setting an XMLEntityResolver to the XMLSchemaLoader that returns
XMLInputSource representing "foo" schema when resolveEntity() is called.

However, I am still getting error messages to stout/sterr.

Any ideas?  What is the best way to handle inlined schemas?

Thanks,

Jeehong Min
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I am trying to obtain XSModels for inlined schemas
in WSDLs.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I am able to do this successfully, except when the
inlined schemas reference each other.&nbsp; For instance, assume I have 2
inlined schemas in the WSDL.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&lt;definitions&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>&lt;types&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&lt;xsd:schema targetNamespace="foo"
xmlns:xsd="..."&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>...</FONT></DIV>
<DIV><FONT face=Arial size=2>&lt;/schema&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&lt;xsd:schema targetNamespace="bar"
xmlns:xsd="..."&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>&lt;xsd:import namespace="foo"/&gt;</FONT></DIV>
<DIV>...</DIV>
<DIV><FONT face=Arial size=2>&lt;/schema&gt;</FONT></DIV></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>&lt;/types&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2>&lt;/definition&gt;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Some type declarations in "bar" schema reference
elements in the "foo" schema.&nbsp; As a result, when I try to load the schema
for "bar" schema, I get an error saying that it cannot resolve the name
"nsBar:Something" when nsBar is the prefix for "bar" namespace.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I am doing this:</FONT></DIV>
<DIV><FONT face=Arial size=2>loader is instance of XMLSchemaLoader</FONT></DIV>
<DIV><FONT face=Arial size=2>SchemaGrammer grammar = loader.loadGrammar(source)
where source is the XMLInputSource representing the inlined schema.</FONT></DIV>
<DIV><FONT face=Arial size=2>XSModel model = grammar.toXSModel()</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I've tried setting an XMLEntityResolver to the
XMLSchemaLoader that returns XMLInputSource representing "foo" schema when
resolveEntity() is called.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>However, I am still getting error messages to
stout/sterr.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Any ideas?&nbsp; What is the best way to handle
inlined schemas?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Thanks,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Jeehong Min</FONT></DIV></BODY></HTML>