Re: JAXP, validation, schemas

Elena Litani wrote: > > Summary: > > The new schema language property should define the value of "ANY" to > allow validation based on the grammar found in document instance. > Otherwise, the property may be set to the namespace of a schema against > which validation must occur (reporting

Re: Xerces-J 2.0.0 beta 4 coming soon

Elena Litani wrote: > > Edwin Goei wrote: > > > Currently if validation feature is set to true and document has no > > > grammar, the parser reports validation error. > > > > Yes that is true. However, if the doc only has an XSD grammar, then no > > validation error is reported which does not co

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] writes: > 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

Re: JAXP, validation, schemas

> Summary: > > The new schema language property should define the value of "ANY" to > allow validation based on the grammar found in document instance. > Otherwise, the property may be set to the namespace of a schema against > which validation must occur (reporting validation errors, an

[ANNOUNCEMENT]: Xerces-J 2.0.0beta4 now available

Hi folks, Perhaps it came as a surprise to people on this list that we got beta4 out today despite having spent the whole weekend not even being able to parse our own build file... As the author of that screwup I can say it was (fairly) straightforward to fix. Anyway, just wanted to apologize

Re: DOM performance question

[EMAIL PROTECTED] wrote: > > 1) I'm groveling through the Xalan code, looking for performance > bottlenecks, and I've noticed something a bit odd. Most of the DOM > operations which get a value from a node -- getNodeName, getNodeType, etc. > -- are returning in a relatively small number of ticks.

[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 b

Brainstorming: lookup by Node Identity

While the DOM WG seems to have dropped the concept of a "node key" which could be used to build lookup tables based on node identity (last I knew, they were talking about reintroducing something like userData instead, though that's just the API level and the implementation might use keys), Xalan w

DOM performance question

1) I'm groveling through the Xalan code, looking for performance bottlenecks, and I've noticed something a bit odd. Most of the DOM operations which get a value from a node -- getNodeName, getNodeType, etc. -- are returning in a relatively small number of ticks. JProbe reports the "line time" for

DO NOT REPLY [Bug 5461] - DefaultEntityHandler.expandSystemID() returns "", causes JAXP 1.1 violation in xalan

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 4973] - xerces2b3: line breaks within CDATA are discarded

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5461] - DefaultEntityHandler.expandSystemID() returns "", causes JAXP 1.1 violation in xalan

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5216] - Only get first line of multiline CDATA section

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5465] - can't validate xml using xsd

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5465] New: - can't validate xml using xsd

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: object serialization

> Hi all > > Had to fix ParentNode::readObject when deserializing-got a NullPointer > Exception. This works, but it I am not certain of all it does. > > /** Deserialize object. */ > private void readObject(ObjectInputStream ois) > throws ClassNotFoundException, IOException { > >

DO NOT REPLY [Bug 3449] - auto change the existing encoding to wrong encoding

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5360] - DOMCharacterDataModifired don't work properly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5461] New: - DefaultEntityHandler.expandSystemID() returns "", causes JAXP 1.1 violation in xalan

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 5080] - defaultValue parameter of attributeDecl not null

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Xerces-J 2.0.0 beta 4 coming soon

Edwin Goei wrote: > > Currently if validation feature is set to true and document has no > > grammar, the parser reports validation error. > > Yes that is true. However, if the doc only has an XSD grammar, then no > validation error is reported which does not conform to the XML REC. Are you tal

DO NOT REPLY [Bug 5460] New: - Definitions in Included schemas (yet to be processed) not in scope

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Xerces-J 2.0.0 beta 4 coming soon

Elena Litani wrote: > > > I'd vote for fixing the _default_ behavior that an app can set the SAX > > "validation" feature to true and yet not get any validation errors if > > the instance doc does not contain a doctypedecl. See my other recent > > posts on this subject. > > Currently if validat

Re: Xerces-J 2.0.0 beta 4 coming soon

Glenn Marcy wrote: > > >Currently if validation feature is set to true and document has no > >grammar, the parser reports validation error. > > I am still thinking that if the validation feature is set to true, > and the document has no DTD grammar, that the parser must report > DTD validation e

Re: Xerces-J 2.0.0 beta 4 coming soon

>Currently if validation feature is set to true and document has no >grammar, the parser reports validation error. I am still thinking that if the validation feature is set to true, and the document has no DTD grammar, that the parser must report DTD validation errors, even if the document has a

Re: Xerces-J 2.0.0 beta 4 coming soon

> I'd vote for fixing the _default_ behavior that an app can set the SAX > "validation" feature to true and yet not get any validation errors if > the instance doc does not contain a doctypedecl. See my other recent > posts on this subject. Currently if validation feature is set to true and doc

Re: Xerces-J 2.0.0 beta 4 coming soon

Joe, [EMAIL PROTECTED] wrote: > ... Just want to renew my request for a simpler way to get incremental SAX > parsing. The sequence we've been given for use from Xalan does seem to be > working now. We will consider this request for the next release. I don't think we should / can put something i

Re: Problem using xalan with xerces2

Have you tried the latest code from CVS? We removed a default that was forcing incremental mode any time Process.main() was writing to Standard Output, and found and fixed an initialization problem in Xerces2 incremental. As far as I know, we should now be functioning with Xerces2. If there are

DO NOT REPLY [Bug 5084] - Effect of StandardParserConfiguration.setDocumentHandler

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Xerces-J 2.0.0 beta 4 coming soon

>So if any one has outstanding code to put down that they want included >in the next release, ... Just want to renew my request for a simpler way to get incremental SAX parsing. The sequence we've been given for use from Xalan does seem to be working now. But the fact that Andy himself left out

Re: JAXP, validation, schemas

Kohsuke KAWAGUCHI wrote: > > First of all, I could not find anywhere in JAXP specs that setting > > setValidation() sets validation against DTD. > > So it was parser/implementation specific. > > Maybe so, but I guess when JAXP is developed, "validation" implied > nothing but DTD, since there wasn

[GUMP] Build Failure - Xerces2 dist

This email is autogenerated from the output from: Buildfile: build.xml BUILD FAILED Error reading project file Total tim