Using Visual Studio I link my application against Xerces and ICU. If I use either of those specific classes in my code I get unresolved link errors. The other exception types are exported in the API's and I have no problem with those. In fact, when I check the xerces dlls with a depends tool, neither of these two classes are exported. The header file confirms this.
Ultimately I need to create my own versions of the scanners and parsers because the current implementation of xerces does not provide enough hooks to uri-ids to namespace names, then resolve the namespace name to a grammar. All these APIs are private in SAX2. So I need to either implement my own classes (which results in the above link errors), or modify Xerces to suit. Bob At 01:25 PM 5/14/2002 -0600, you wrote: >"Robert Buck" <[EMAIL PROTECTED]> writes: > > > I am wondering if the following classes can be exported by default by > > the Xerces API: > > > > > > SAXNotSupportedException > > SAXNotRecognizedException > >Hi Robert, > >What is the problem, exactly? I use these in my code without >dificulty. Please explain. > >jas. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
