determining the encoding of an external subset via XNI

Hi all, In an attempt to generate some more discussion surrounding the issue I raised in the message below, here are some ways by which we might move forward. For those who didn't see the previous thread, the Cole's Notes version of the problem is that, as XNI is currently designed, there doesn't

Re: Converting XML Schemas

Hello, Once XML Schema 1.1 does come out, this will be a very excellent question and hopefully some resources will be forthcoming to help answer it. But the version of XML Schema from 2001 is the only version of XML Schema that any production system should be using; all previous versions were not

Re: unable to redefine attributeGroups

Hi Eric, Your syntax was close, but not quite right. The trick is that, instead of repeating the content of the attributeGroup you're redefining, you have to explicitly reference it; here's a redone b.xsd that exemplifies this (and that Xerces is happy to validate). (See attached file: b.xsd) H

RE: Xerces 2.3.0 and *apis.jar

Hi Harald, In an ideal world, there shouldn't even be differences in the builds of the xml-apis.jar that Xerces and Xalan both ship. We haven't quite gone that far yet, though, so even if we generate off of the same source, it'll likely be different JDK's doing the building so the jars' bytecode

RE: Xerces 2.3.0 and *apis.jar

Hi Harald, Michael's guess is correct. We made a decision during the development of 2.3.0 to source our API's from (a branch of) xml-commons, in order to ensure the API's we rely upon sync up exactly with what corresponding versions of Xalan, in particular, rely upon. But, since we've been distr

Re: Bug in 2.3.0?

Hi Alex, Well, it's possible you've found a bug; I think it's fair to say that the xerces-specific schemaLocation properties don't tend to get tested as well as many other aspects of the parser... I'd recommend two things: 1. Give us a cut-down test-case that reproduces the problem; 2. If you

[ANNOUNCEMENT]: Xerces-J 2.3.0 now available

Hi all, The Xerces-J team is very happy to announce that version 2.3.0 of Xerces-J is now available. With this release, the Xerces-J developers are declaring the Xerces Native Interface (XNI) core and parsers packages to be gold. This release also brings Xerces-J into compliance with the most rec

Re: encoding and saxparser

Hi Joseph, I had a feeling something like that might have been the case. I'll bet there's some difference in the way you're viewing the SAX output as compared to the DOM output. If you look at the integer values of the chars your ContentHandler is getting, I'll bet 63 (0x3f) isn't among them...

Re: encoding and saxparser

Hi Joseph, In order to be of help, we'll need to know exactly what behaviour you're observing, how you're observing it, and why it's at variance with what you expect. Thanks, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED]

Re: encoding and saxparser

Hi Joseph, That's a good question; its answer will depend at least on what version of Xerces you're using and exactly what the SAXParser is doing. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |-+-

Re: Class SecuritySupport and Class.forName("java.security.AccessController")

Hi Annette, While your modification should work for your application, it won't work in general because querying system properties is (potentially) an operation requiring privilege. The whold point of the SecuritySupport classes is to determine if the concept of operations requiring privilege exis

Re: Turning off DTD validation but allow Schema validation ( was Re: Schema validation with Xerces and JAXP )

Hi Jesus, This is a schema validation error. (You can tell; cvc == complexType validation constraint). It's produced when Xerces can't find your schema file. Usually this means that something went wrong with Xerces's attempt to resolve the location of the file, but other things could be wrong a

Re: New xercesImpl compatible with java 1.1

Hello, Just to add one point to Joe's note: It is still a goal for Xerces to run under 1.1.8, but we can no longer compile there. This is unavoidable, unfortunately, because of some J2EE issues we had to take into account for internal classloading. The unfortunate part is that this makes preser

Re: Dos Attack via Xerces

Hi Robert, In Xerces2 CVS, a feature has been implemented called http://apache.org/xml/features/disallow-doctype-decl which, when set to true by an application, causes Xerces to emit an error upon detection of a doctype and refuse to process the document. The DOS in question involves enti

Re: old version of xerces

Hi Didier, Your best (only?) choice is to use CVS to grab sources corresponding to the tag that, one would hope, was used as the source for 1.1.2. The tag you want is Xerces-J_1_1_2. Hope that helps! Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mai

Re: Bug with SAX reader.parse(Reader r)

Hi Henry, This "bug" got reported so many times, we finally wrote a FAQ about it a while back: http://xml.apache.org/xerces2-j/faq-general.html#faq-8 Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |-+-

RE: EntityResolver question

Hi Linh, A couple of things: I notice you say "I also set "schemas" in the manifest so getResourceAsStream should be able to read the document." Are you sure that it actually *does* read the document though? If it hands Xerces a null reference, there's not much it can do... Once you're certain

RE: EntityResolver question

Hi Benson and Linh, The reason Xerces now returns fully-expanded URI's to the Entity resolver is that SAX quite explicitly states that this is what XML processors are supposed to do. The behaviour in 1.4.4 was a bug. The most portable behaviour is to use absolute URI's in your schema, then map t

Re: LinkageError with 2.2.1 - really simple project (Can't xerces built either)

Hi Ryan, The compilation problem is a known issue with the 2.2.1 tools distro; you can do a CVS checkout if you have enough interest. But recompiling Xerces is pretty unlikely to resolve your basic problem: You might want to try recompiling your project against the Xerces binaries you downloaded

RE: UTF-8 encoding question

Hi Benson, In XML 1.0, the point of being able to use character references (such as Ò) is so that the Unicode characters to which they correspond can be referenced even in documents whose encoding doesn't permit the expression of those Unicode values. When the parser sees such a reference, it is

Re: Verifying DTD

Hi Simon, The grammar caching API's that Xerces provides do allow you to preparse an external subset and use it to validate an incoming document. This isn't 100% full-featured yet; entities don't work well. But this might be a start for you anyway. For details, see the oft-cited "grammar parsin

Re: "Content not allowed in prolog" returned when attempting to parse document encoded in UTF-16

Hi Ryan, It'll definitely be necessary to see the document that's giving you problems. Sending it as a zipped attachment would be preferred, since that way we'll know we're getting the original you're testing with. Thanks, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3

Re: problems with spaces and special characters...

Hi Panos, Most of Xerces parsing methods expect URI's, which can't contain spaces. If you want to use such methods, you need to escape the space characters with %20 as mandated by the URI specification. The only exception to this are the JAXP parse(File) methods, where Xerces will convert the nam

Re: KEY-KEYREF validation

Hi Markus, Seems you haven't set the http://xml.org/sax/features/validation feature anywhere; this needs to be set for Xerces to report errors. The JAXP setValidating(boolean) methods have the same purpose. Another question I have is: if you only care about speed, why not use SAX? Most of your

RE: finding the version used ...

Hi all, In xerces2 it's org.apache.xerces.impl.Version. Yes, working on the MANIFEST is a good idea; it'll get done eventually no doubt, but if anyone wants to send a patch to solve this simple problem, it'd be welcome. :) Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone:

RE: Parsing XML Containing Euro Sign

Hi Chris, Wonder if you could recover the details of the problem you had with the 8859_1 transcoder. Every JDK is obligated to support at least the "canonical" transcoder names; and that's what we *should* be using. I can't imagine how this kind of situation could arise except if we aren't using

Re: Schema key and unique contraints VERY slow

Hi Eric, You'll definitely want to move to 2.2.1; a fair bit of work has been done on improving performance (and conformance!) of identity constraint support since 2.0.2. That said, I can't say I'm shocked that you're not seeing good performance. If you have N distinct keys in your document, Xerc

RE: question about new release 2.2.1

Hi Alex, I guess Sandy's still thinking about it. Patches always welcome! :) Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |-+> | | "Aleksandar | |

Re: question about new release 2.2.1

Hi Alex, Hmmm; perhaps it was just the noNamespaceSchemaLocation property... See [1]. Oh well, 2.2.1 is a considerably better product; it's worth the upgrade. :) Cheers, Neil [1]: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13719 Neil Graham XML Parser Development IBM Toronto Lab Phone:

Re: problem with dom3 and jdk1.4

Hi Romain, Two quick points: 1. The endorsed standards override mechanism lets you use environment variables if you don't want to modify the JDK installation. This should be relatively portable and painless, especially since only the environment of the user needing to use the modified process ne

Re: XMLGrammarBuilder bug?

Hi Henry, Sandy and I talked about this, and we can't figure out why it appeared to work last week; nothing's changed in the code and this seems to be the behaviour it always exhibited... All that to say: yeah, it'd be a neat idea to validate sans presence of a DOCTYPE line; but evidently it's s

[ANNOUNCEMENT]: Xerces-J 2.2.1 now available

Hi everyone, The Xerces-J team is pleased to announce the availability of Xerces-J 2.2.1. As well as containing a few performance improvements and many minor bug fixes, four bugs which a number of users encountered with version 2.2.0 have been resolved: Fixed SAX endElement call so that the ele

Re: compatibility / difference between xml-api.jar and xmlParserAPIs.jar

Hi Joe and all, Just a small point to add to your message: we are a bit out of sync with Xalan at the moment, actually. We've gone ahead and improved the robustness of our JAXP code in terms of handling files--especially when the filenames contain spaces or non-ASCII characters. We've actually

Re: using XML schemas embedded in other files

Hi Jeff, The trouble with embedded schemas is that it's not at all clear what their semantics should be. For instance, should it be the case that a parser should automatically start building a schema, whenever it sees an element named from the http://www.w3.org/2001/XMLSchema namesace? Should t

RE: Class Cast Exception

Hi Rob, Well, Xerces releases have existed where org.apache.xerces.parsers.SAXParser didn't implement XMLReader. They're *really* old, and I can't imagine how you'd run into one, but I wonder if it's possible that you've got some kind of strange situation where, somehow, the first class by this n

Re: symbol table

Hi Alex, Xerces symbolTable calls String.intern() on anything passed in, so if you simply intern the strings you want to reference-compare, you should be off to the races. Failing that, you could try the getAttribute method on the DocumentBuilderFactory/SAXParserFactory cdlasses in JAXP; I have t

Re: Internationalization of parsing error messages

Hi Wyn and Andy, A few points to keep in mind: 1. The XML4J on alphaworks (4.0.6, IIRC) is descended from Xerces 2.0.0, but it's a pretty distant relation. If you wait a couple of weeks there should be a version posted that descends from Xerces 2.2--and the message translations may well have be

RE: Re: AW: Not an FAQ: still unable to validate against XSD

Hi John, All jars--including the xerces-related jars--from the tools package aren't meant for production; they're just meant to help build xerces. So if the jar you're using came from there, you're (1) not using Xerces 2.2 and (2) quite possibly using something that's broken. It does what we nee

[ANNOUNCEMENT]: Xerces-J 2.2.0 now available

Hi all, The Xerces-J team is pleased to announce the availability of Xerces-J 2.2.0. As documented below, two changes to the Xerces Native Interface have been made in this release. Performance improvements and a host of bugfixes comprise the remainder of the changes contained in the release. Spe

Re: What version of xerces is used?

Hi all, I can see the possibility for confusion here: In Xerces 1.x, the relevant class was org.apache.xerces.framework.Version; in Xerces 2.x it's org.apache.xerces.impl.Version. In 2.x, getVersion is the relevant method; in 1.x, the fVersion String was what you'd want to look at. Hope that he

Re: filenames versus URI's

Hi again Elliotte, As an addendum to my last note, there is one consequence of this discussion for JAXP: The horribly broken way it currently produces a URI from a File needs to get fixed. (See the parse(File) classes from either DocumentBuilder or SAXParser in either our code or xml-commons.)

Re: filenames versus URI's

Hi Milind, The main reason this has come up is the wide variety of situations we're being asked to handle viz. filename conversion. So we're asking the question of whether we should be in the business of offering these services at all: Sure they're useful, but we're an XML parser and, surely, th

Re: filenames versus URI's

Hi Elliotte, Firstly, this isn't just an API issue. If someone presents us with a document containing something like xsi:schemaLocation="http://my.com c:\My%Schema.xsd" then we need to decide whether to try and "fix" the filename or simply reject it. Same goes for systemId's in a DOCTYPE

filenames versus URI's

Hi all, There are a number of places where the parser has to interact with the file system (e.g., in resolving systemId's, schemaLocation hints and Strings supplied to our JAXP #parse methods.) To my knowledge, all of these situations are expecting a URI--possibly relative--rather than a filename

Re: [ANNOUNCEMENT]: Xerces-J 2.1.0 is now available

Hi Paul, cc'ing the xerces-j-user list, since that's probably where we should take this discussion. I have a feeling you probably already know this, but the Schema for Schemas certainly isn't needed to use Xerces to validate a schema without an instance document. (In fact, although the Schema fo

[ANNOUNCEMENT]: Xerces-J 2.1.0 is now available

Hello all, The Xerces-J team is pleased to announce the availability of Xerces-J 2.1.0. While there have been some relatively minor changes to the Xerces Native Interface (as documented below), this release has focused primarily on filling out gaps in function--such as in the experimental DOM lev

Re: xmlvalidator does not detect violations of uniqueness

Hi Michael, This is part of the XPath 1.0 recommendation. From [1]: [[ A QName in the node test is expanded into an expanded-name using the namespace declarations from the expression context. This is the same way expansion is done for element type names in start and end-tags except that the defa

Re: xmlvalidator does not detect violations of uniqueness

Hi Marv, Some while back, Eddie Robertson posted a message where he diagnosed this problem in another user's schema; perhaps a trip through the archives could have dug out that note. But the problem is non-obvious, so it's no doubt worth posting the cause again: The default namespace isn't used

Re: passive grammar caching + external schema locations

Hi Alex, Sorry for the slow response... Let me take a stab at both your messages: >1. Can passive grammar caching work when the external-schema-location >property is set? I hope so. >If yes, what happens when this property is set again to a >different value? Xerces always looks at its gramma

Re: Schema validation

Hi Peter, Well, you can't exactly convert schema files into .class files with Xerces, but you can certainly get the parser to compile them into an internal representation which it can then use to validate multiple instance documents. (In fact, you can do this with external DTD subsets too!) For

Re: Xerces compilation under JDK 1.1.8

Hi Andy, Specifically, I'm referring to the modifications Edwin made to the JAXP factory code on a branch of xml-commons to ensure that the FactoryFinder can work pretty much anywhere it would need to be employed (i.e., embedded in JDK's, application servers, or deployed as part of a standard appl

Xerces compilation under JDK 1.1.8

Hi folks, Some time ago, the idea of formally abandoning support for JDK 1.1.8 was floated. It didn't go over well: We got feedback that there are significant numbers of users who still are dependent on 1.1.8, so abandoning support for running on that VM isn't an option for now. But, are there

Re: Progressive parsing

Hi Paul, I saw your post on general@ and meant to respond there, but never got around to it; sorry about that. What I was going to suggest is that you may wish to look at http://xml.apache.org/xerces2-j/faq-grammars.html which should at least help with your DTD reuse question. If you were usin

Re: Validating a schema is a valid schema

Hi Brian, When you want to validate a schema by itself, it's always useful to remember that, even if Xerces were able to handle the schema-for-schemas with no difficulties, you still wouldn't get complete validation of your schema by directly referencing it. There are all kinds of schema-validity

Re: grammar cache -> necessitates existence of top-level schema for a namespace

Hi Alex, Glad to hear the grammar caching code is working for you--it's all pretty new, so I'm betting there's still a bug or two lurking around in it... As background, the reason Xerces assumes it will only have to contend with one grammar from a given namespace is that it makes our implementati

Re: caching of grammars that include other grammars

Hi Torsten and Alek, You're not being ignored--it was a long weekend up here in Canada, so I haven't been on line to see these messages. Now I'm here, so I'll try and answer: The first problem you found--where an included schema would be flagged as being in error for having a non-identical names

Re: Problems with Xerces in Japanese Environment

Hi Una, Xerces 2.0.2 has mappings from WINDOWS-31J to MS932. So if you're using this version of Xerces you shouldn't have any trouble. If you're still using Xerces1, I'd strongly urge you to upgrade if you can; there hasn't been a release on the Xerces1 base in over 6 months and there's every re

Re: DocumentBuilderFactory's setAttribute() no longer working properly in xerces 2.0.2 ??

Hi Eric, Hmmm; no, that jar should have had it--the "fix" went in on Monday. Could you send a test-case? The one we have passes. Thanks, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |+--

Re: DocumentBuilderFactory's setAttribute() no longer working properly in xerces 2.0.2 ??

Hi Eric, Yeah, it's too bad the JAXP 1.2 problem wasn't caught sooner; there may well be a 2.0.3 to fix it. The space-before-amp problem has been there for ages though and you're the first to notice it; so that wouldn't have been a stop-ship in any event... As to gump jars: Pretty much the only

Re: DocumentBuilderFactory's setAttribute() no longer working properly in xerces 2.0.2 ??

Hi Dave, This is a known regression and is already fixed in CVS. You can either do a CVS checkout and do a build manually, or you can look at http://gump.covalent.net/jars/latest/xml-xerces2 which should have a snapshot incorporating this fix by now. Cheers, Neil Neil Graham XML Parser De

Re: Parsing a DTD using the org.apache.xerces.parsers.DTDParser Clas s..

Hi Sateesh, I don't believe there is a concrete extension of this class in Xerces (in fact, I once proposed we get rid of this class because I thought it might confuse people. :-)) You might want to take a look at org.apache.xerces.parsers.XMLGrammarPreparser and org.apache.xerces.impl.dtd.XMLDT

Re: followup: SAX loses space before &

Hi Eric, I think Elena has a fix in mind for this, but she wasn't sufficiently confident it didn't havde side-effects for it to go in 2.0.2. She's pretty busy this week, so it might not be until next week before this gets fixed in CVS... Cheers, Neil Neil Graham XML Parser Development IBM Toront

Re: Xerces 2.0.2 is now available!

Hi Gopal, Thanks for pointing this out; I remembered to fix all the files but I forgot we'd created some new directories as well :-). Should be fixed now. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] |+-

Xerces 2.0.2 is now available!

Hi all, The Xerces-J team is proud to announce that Xerces-J 2.0.2 is now available. In this release, numerous bugs have been fixed. Only one minor change in the Xerces Native Interface is included (documented below); considerable new functionality has also been added in terms of PSVI support, DOM

RE: problem with DTD

Hi Dominique, >From a purely technical standpoint, I think Xerces now has the infrastructure to do what you want to do-we can now build a DTD grammar from an external DTD independent of an instance document, and we can apply that grammar to different instance documents. (See the new xml-grammars

RE: utf8 encoding - second itaration

Hi Jaro, Sorry; I thought you hadn't noticed the 'j'--you wouldn't have been the first. Xerces-C has only one list; you can get subscription info from the "mailing lists" link off http://xml.apache.org. HTH, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-35

Re: utf8 encoding - second itaration

Hi Jaro, Since you're using Xerces-C, if you post to a Xerces-C list you'll probably find someone to help you. This list is for Xerces-J. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED]

Re: SAX parser class loading

Hi Edwin, Let me see if I can summarize where we're at here (and explain to myself why Rob's code works for him if Edwin's right about what's going on). If Rob's on a Sun JDK 1.4.x and doesn't use the endorsed standards override mechanism, he should break if Edwin's right because he'll pick up Cr

Re: what does the ur-type need: strict, lax or skip validation?

Hi Evgueni, Odd; I just addressed this same issue for someone else in private correspondence yesterday. So I have the info handy: In the Schema for Schemas, the ur-type (called anyType there) is defined to have a wildcard element with no processContents attribute specified- Since this defaults

Re: ^M in an XML Content

Hi Bruno, According to the XML 1.0 spec, xerces has to do end-of-line normalization; so it will tend to consume your 0xd's. But even if you are using EBCDIC on an early Sun JVM, it's very hard for me to see how xerces would manage to "ignore" sections of your document... Since xerces 1 isn't act

Re: Parsing element names.

Hi Morten, This is all thoroughly xerces-specific of course, but take a look at the org.apache.xerces.util.XMLChar class. I think the isValidName method may do what you want. Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMA

Re: Validating XML documents using the Xerces parser

Hi Simon, The deal is this: the SAX validation feature was developed in the days of DTD's. When you turned it on, it meant "report validation errors" so for a document with no DTD--which, by the XML 1.0 spec is invalid--we'd have to report errors. i.e., on a schema-valid document we'd have to r

Re: Initial questions

Hi Mike, The IBM JDK will contain XML4J (of course a very close relative to xerces) as of JDK 1.4. Whenever the JDK adopts JAXP 1.2 as an integral part, it would appear Sun will have little option but to adopt xerces as well since Crimson doesn't contain the schema support that JDK 1.2 requires.

RE: UTF-16 not supported?

Hi Eric, I'd have to see your document to be more specific. From your description, I can't tell exactly what you're doing to convert your original document to UTF-16. The other thing you could do is look up the UTF-8 representation of the Unicode character you want; this should enable you to kee

Re: UTF-16 not supported?

Hi Eric, You're actually seeing one of Xerces1's less helpful eccentricities. When it reads a document that claims to be in UTF-16 but which has some problem, Xerces1 tended to claim not to support the encoding--instead of pointing out where the error is. I believe this behaviour no longer exist

xerces and schema identity constraints

Hi folks, Noticing the recent flurry of queries and bug reports concerning Xerces support of aspects of schema identity constraints, I thought it would be useful to let the community know that this stuff is going to be revisited very soon. Identity constraint validation is about the only portion

Re: Dumb question, I hope

Hi Steven, The document your message contains passed through Xerces 2.0.1's samples as far as I tried them. I also tried with Xerces 1.4.4 and had no problems. Are you trying to validate this document against a schema or a DTD? I tried with validation turned off of course. If so, then we'll nee

RE: XmlSerializer putting xmlns="" on children of root element

Probably because you're using a locally-declared attribute in your schema and you don't have attributeFormDefault set to qualified in the schema. But again, I didn't look at the schema excerpt you posted, so this is a conjecture. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Pho

RE: XmlSerializer putting xmlns="" on children of root element

Hi Eric, I haven't been tracking your posts as closely as I Might, but I do notice one misconception that I think might be getting in your way. Consider http://my.com"; b="myAttribute"/> Here, element a is indeed bound to the http://my.com namespace. But the attribute b is *not* in that namesp

Re: XmlSerializer putting xmlns="" on children of root element

Hi Eric, Right; as Neeraj and Pavani have pointed out in various messages lately, the latest jars can be had from: http://gump.covalent.net/jars/latest/xml-xerces2/ HTH, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED]

Re: XmlSerializer putting xmlns="" on children of root element

Hi Eric, What version of Xerces are you using? A number of serializer bugs have been fixed recently, so it might pay to do a CVS extract to obtain the most recent code. (Or you can obtain recent jars from http://gump.covalent.net, if I have the URL correct.) Cheers, Neil Neil Graham XML Parser

RE: External ENTITY Reference Behavior with X1/X2/SAX

Hi Andy, (B (BFWIW, I think you're analysis is entirely correct and I've been meaning to (Blook into this for the last couple of months--ever since I put down the (BrewindableInputStream. :-) It's just that other things kept rising higher (Bon my priority queue, and for some reason I had tho

Re: can't validate xml using xsd

Hi Malia, Try setting all three of these features to true and you should be set. http://xml.org/sax/features/namespaces http://xml.org/sax/features/validation http://apache.org/xml/features/validation/schema More info about this can be found in the features document (http://xml.apache.org/xerces

Re: [ANNOUNCEMENT]: Xerces-J 2.0.0beta4 now available

Hi Kevin, >From the very end of that admittedly rather long announcement: It should be borne in mind that some classpath changes may be required on the part of users as xerces-J 2 development moves forward, since the community has decided to separate the API's that we support and their implementa

[ANNOUNCEMENT]: Xerces-J 2.0.0beta4 now available

Folks, The Xerces-J team is very happy to be able to announce the availability of the fourth Xerces2.0 beta. While a very considerable amount of development has been undertaken since Xerces-J 2.0.0 beta3, we are very confident that the product is near production quality. This should prove to be

Re: UTF Encoded XML docs and Xerces SAX (1.4.4)

Hi Ashish, Unfortunately it's not clear to me what you're after here. Shouldn't ä map to a single unicode character--i.e., not bbe split between two chars? It might be useful to make sure you're viewing the result of the characters (...) callback in the same way that the browser is displaying it

RE: [xerces2] info about some packaging changes

Hello, We considered this approach actually. At least these two things scared us off: First, this might be a little interesting with regard to building and testing. The big one though is that we weren't convinced that we could guarantee that our DOM implementation wouldn't end up having to use

[xerces2] info about some packaging changes

Hi folks, I'd like to get your feedback on a couple of relatively minor changes some of the committers think need to be made (indeed, some of them have been already checked in :-)) and give everyone some background as to why they appear to be necessary. Naturally, this pertains to Xerces2. As

RE: [ANNOUNCEMENT]: Xerces-J 1.4.4 released

Hi Ivan, Which site did you go to? If you go to http://xml.apache.org/dist/xerces-j/ you'll find all the files there. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Uthus Ivan <[EMAIL PROTECTED]> on 11/19/2001 10:

[ANNOUNCEMENT]: Xerces-J 1.4.4 released

Hi all, The Xerces-J team is pleased to announce the release of Xerces-J 1.4.4. Since Xerces2 is not yet production-grade, and since we haven't put out a bugfix release of Xerces1 in over two months, we thought it was time to put out such a release. This release includes: - JAXP fixes. [Edwin G

[ANNOUNCE]: Xerces2-J Beta3 released

Hello all, The Xerces-J team is very pleased to announce the release of the third Beta release of Xerces2-J. This release fixes a number of bugs, introduces some changes to the Xerces Native Interface, and is the first Xerces2 release to include XML Schema validation support. Please note that th

Re: Validating Documents with Relative Schema 'includes'...

Hi David, Philip and Chad: I'm surprised that a trip to the archives--which surely haven't been down for a whole week...--didn't elicit an answer to this popular question :-(. Anyway, since it's impossible for the parser to be all things to all people in terms of resolving the locations of entitie

Re: Is it possible to redefine schema elements?

Hi Vlad, No, you can't do that. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] on 10/18/2001 05:40:16 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Is it possi

Re: Is it possible to redefine schema elements?

Hi Vlad, No, you can't redefine elements. But since you can redefine the type of the element in question--if it is of a named type that is--by simply redefining the type you'll have redefined the element. Remember that it's the redefined type that's used with an element in the redefined schema,

Re: Xerces 1.4.0 with JDK1.1.8

Hi Alan, You're right; due to an oversight, Xerces 1.4.0 didn't compile under JDK 1.1.8. But, so far as I know, all three versions of Xerces 1 that were released since do compile under that JDK. So perhaps you could try downloading one of them--Xerces 1.4.3 is the most recent. Cheers, Neil Nei

Re: getElementById Question

Hi Christian, Yes, as far as I know, that's true. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Christian Geuer-Pollmann <[EMAIL PROTECTED]> on 09/28/2001 04:31:37 PM Please respond to [EMAIL PROTECTED] To: [E

Re: cannot resolve symbol MUTATION_ALL

Hi Otis, Looks like you might have a classpath problem. There isnt'an org.apache.xerces.dom.ChildAndParentNode class in Xerces anymore--at least not in the CVS version I have in my computer. IIRC, it was removed a long time ago, certainly before 1.4.0. So my advice is to a) look very carefully

Re: getElementById Question

Hi Christian, There's no way with DOM level 2 to validate a DOM tree. So, unless you can wait for DOM level 3, which will have this support, you're best bet will probably be to serialize your DOM tree into an in-memory structure like a byte array and then direct an InputSource at that structure.

Re: Derived types, SubstitutionGroup, Keys and Keyrefs

Hi John, I can't help with your other problem, but I think this is straightforward. When you use an element from some element's substitutionGroup, you literally get that element. So any key which is looking to match on the element you're substituting for can't match, because you've substituted a

RE: Schema error: sch-props-correct: Duplicate declaration for a type ReadCodeType

Hi Nathan, Actually, the string the parser looks for is source.getPublicId()+","+source.getSystemId() where source is what's returned by the user's (or the default) EntityResolver. If source.getPublicId returns null then you get just "," +source.getSystemId(). So if your systemId's are al

  1   2   3   >