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.
Serious issue/challenge with Xerces-J the XSLoader 's loadInputList method...

Serious issue/challenge with Xerces-J the XSLoader 's loadInputList method...

2006-11-25       - By Bullotta, Rick

Hello, all.

Here's a quick summary - the WSDL below contains two schema elements.  I
want to create an XSModel that represents this WSDL, and the only way I
can see to do so is by extracting the schema elements separately,
turning them into LSInputs, and using the loadInputList method on the
XSLoader class.  Unfortunately, it does not work - there is always an
error attempting to resolve the n0:YYY type when it attempts to create
the XSModel.

If I separate the first schema element into its own file, and import it,
it works fine. However, it should work fine in the same file as well!
:-(

I suspect it has something to do with the fact that imports within the
same "file" (in the case of loadInputList, of course, they are separate
sources), would not have a schemaLocation attribute on the import, but
only a namespace attribute (as below).  I am at a loss to determine how
to handle this with Xerces.

In this case, I would expect Xerces to simply see if a model or grammar
has already been loaded for that namespace.  I tried as hard as I could
to trace through the source, but I was completely lost working through
the intricacies of how these things are resolved.

Help!!!

- Rick Bullotta
 SAP Labs, LLC


<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style"
xmlns:n1="urn:sap-com:document:sap:rfc:functions">
  <wsdl:types>
    <xsd:schema attributeFormDefault="qualified"
targetNamespace="urn:sap-com:document:sap:rfc:functions"
xmlns:tns="urn:sap-com:document:sap:rfc:functions"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:complexType name="YYY">
        <xsd:sequence>
          <xsd:element name="Param1"
type="xsd:string"/>
          <xsd:element name="Param2"
type="xsd:string"/>
          <xsd:element name="Param3"
type="xsd:string"/>
        </xsd:sequence>
      </xsd:complexType>
    </xsd:schema>
    <xsd:schema attributeFormDefault="qualified"
targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style"
xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style"
xmlns:n0="urn:sap-com:document:sap:rfc:functions"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <xsd:import
namespace="urn:sap-com:document:sap:rfc:functions"/>
      <xsd:element name="ZmsWsXmiiTest1">
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element
name="Param" type="n0:YYY"/>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="ZmsWsXmiiTest1Response">
        <xsd:complexType>
          <xsd:sequence/>
        </xsd:complexType>
      </xsd:element>
    </xsd:schema>
  </wsdl:types>
  <wsdl:message name="ZmsWsXmiiTest1">
    <wsdl:part name="parameters"
element="tns:ZmsWsXmiiTest1"/>
  </wsdl:message>
  <wsdl:message name="ZmsWsXmiiTest1Response">
    <wsdl:part name="parameters"
element="tns:ZmsWsXmiiTest1Response"/>
  </wsdl:message>
  <wsdl:portType name="zms_ws_xmii_test1">
    <wsdl:operation name="ZmsWsXmiiTest1">
      <wsdl:input message="tns:ZmsWsXmiiTest1"/>
      <wsdl:output
message="tns:ZmsWsXmiiTest1Response"/>
    </wsdl:operation>
  </wsdl:portType>
</wsdl:definitions>



---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@(protected)
For additional commands, e-mail: j-dev-help@(protected)