Re: How to check for entity reference in attribute

Michael, Thanks for your quick response. I will use a simple internal parser to detect them. If the xml is wellformed this should not be too complex Thanks, Dick Deneer Op 16 jan 2010, om 23:21 heeft Michael Glavassevich het volgende geschreven: Even if Xerces internally tracked entity

How to check for entity reference in attribute

=UTF-8? !DOCTYPE personnel SYSTEM personal.dtd [ !ENTITY name Big !ENTITY one 1 ] person id=Big.Boss salary=one; namefamilyBoss/family givenname;/given/name emailch...@foo.com/email /person /personnel Regards, Dick Deneer

XMLCatalogResolver

with this behaviour. But maybe someone recognizes this problem already and give me some hints. I using xerces version 2.9.1. Regards Dick Deneer - To unsubscribe, e-mail: j-users-unsubscr...@xerces.apache.org For additional commands

Re: XMLCatalogResolver

testprogram. Regards, Dick Deneer Op 14 jan 2010, om 11:56 heeft Dick Deneer het volgende geschreven: I have a strange problem using an XMLCatalogResolver. I am using a catalog with relative paths like po.xsd. If I run the program with java 1.6 everything goes well. But when I am running

Re: XMLCatalogResolver

it has something to do with timeoutsettings. Dick Deneer Op 14 jan 2010, om 16:54 heeft Dick Deneer het volgende geschreven: I got a little bit further. My entittyresolver gives back a XMLInputSource witj the following properties: fBaseSystemId = file:///Users/dickdeneer/Documents/workspace

Re: Loosing significant space in LSSerializer

have to make choices where to spent the effort. Thanks Dick Deneer Op 21-nov-2009, om 20:07 heeft Michael Glavassevich het volgende geschreven: You should also be able to control whether spaces are preserved by registering an LSSerializerFilter. When I added one to your test program

Re: Loosing significant space in LSSerializer

Hi Benson, As Michael notes, Xerces is now shipped with the serializer.jar (which contains the xalan serializer). If you have this on your classpath it will be used. If you leave it out, then xerces will fall back to it's own (deprecated) one. regards Dick Deneer Op 22-nov-2009, om 21:54

Re: Loosing significant space in LSSerializer

serilalizes doctype nodes). If there is another way please let me know. Thanks Dick Deneer Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven: Have you tried xml:space=preserve? Jake On 11/20/2009 4:36 PM, Dick Deneer wrote: I am still using the deprecated LSSerializer because

Re: Missing PSVI after Validation.

validator I am not sure, but I think you have to use a validitionHandler, Regards Dick Deneer Op 13-sep-2009, om 12:03 heeft ajay bhadauria het volgende geschreven: Hi all, Can anyone point out in the attached file what I am missing because of which I am not getting PSVI info. after validation

Re: Missing PSVI after Validation.

you please also tell me how I can do that ? Regards Ajay --- On Sun, 9/13/09, Dick Deneer dick.den...@donkeydevelopment.com wrote: From: Dick Deneer dick.den...@donkeydevelopment.com Subject: Re: Missing PSVI after Validation. To: j-users@xerces.apache.org Date: Sunday, September 13, 2009

Re: Create a new xml document based on a schema

= xsModel .getComponents(XSConstants.ELEMENT_DECLARATION); Then recursively visit the XSModel to get all elements and attributes. But to do this well it is al lot of work !! Regards Dick Deneer Op 18-nov-2008, om 9:56 heeft chodnik het volgende geschreven: Hi

Re: Creating internal DTD subset with Xerces-J

Are you using a Transformer class to serialize the document ? If so, then try to use the LSSerializer instead to serialize the DOM and you will also have the DTD subset in your output. Regards Dick Deneer Op 13-jan-2008, om 6:29 heeft Mukul Gandhi het volgende geschreven: I found

Re: Creating internal DTD subset with Xerces-J

help ... On Jan 13, 2008 3:49 PM, Dick Deneer [EMAIL PROTECTED] wrote: Are you using a Transformer class to serialize the document ? If so, then try to use the LSSerializer instead to serialize the DOM and you will also have the DTD subset in your output. Regards Dick Deneer -- Regards, Mukul

Re: problem getting typeinformation after using DOMNormalizer

Michael, One more question about this. Do I also have to take in account that an attribute can be removed by the normalizer, or will that never happen? Regards Dick Deneer Op 4-okt-2007, om 5:01 heeft Michael Glavassevich het volgende geschreven: Hi Dick, I wouldn't expect

problem getting typeinformation after using DOMNormalizer

tp://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.donkeydevelopment.com/schema/example test.xsd/ test.xsd Description: Binary data Dick Deneer

Re: problem getting typeinformation after using DOMNormalizer

it is rather tricky to do this while the validation is in progress. I will change my code and remove them afterwards. Thanks Dick Deneer Op 4-okt-2007, om 5:01 heeft Michael Glavassevich het volgende geschreven: Hi Dick, I wouldn't expect the normalizer to have predictable behaviour if some

Re: Losing entity references in attributes

serializer the output is OK. By the way: Can I make a JIRA request regarding to the entity reference issue for attributes. Maybe it is worth reconsidering the made design decision. A similar implementation as in elements, with a property setting, would solve this problem. Dick Deneer Op 18-feb

Re: Losing entity references in attributes

in the serializer to get the userdate of the attributes and put back the original (entity-) value. Suggestion are very welcome Dick Deneer Michael Glavassevich wrote: XNI doesn't report entity boundaries in attribute values. This was a design decision made long before I arrived

Re: Xerces Problem - Compound Schemas - Name Resolution Error

this extra message heps to clearify your problem. Regards Dick Deneer Op 1-feb-2007, om 18:04 heeft [EMAIL PROTECTED] het volgende geschreven: I'm getting a very weird error when using Xerces to parse an XSD document (Xerces as embedded in Oxygen 8.1). E src-resolve: Cannot resolve

XSModel susbstitution question

I have the following schema xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; xsd:element name=root xsd:complexType xsd:sequence minOccurs=1 xsd:element ref=myAbstract/ /xsd:sequence /xsd:complexType /xsd:element xsd:element

Re: DOMNormalizer has problem with abstract types in schema

. This should work now. Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] Dick Deneer [EMAIL PROTECTED] wrote on 01/17/2007 01:31:05 PM: My program relies heavily on the functionality of the DOMNormalizer for editing XML

DOMNormalizer has problem with abstract types in schema

My program relies heavily  on the functionality of the  DOMNormalizer for editing XML in a tree.I think there is problem with schemas containing abstract type definitions.The xml validates OK using standard validation, but the DOMNormalizer returns:Program startedhandleError cvc-elt.4.2: Cannot

Re: DOMNormalizer invalidates XSD files

Thank you for checking this out. Your answer is clear. Dic Deneer Op 15-jan-2007, om 0:39 heeft Michael Glavassevich het volgende geschreven: Dick Deneer [EMAIL PROTECTED] wrote on 01/04/2007 05:29:29 PM: I am using the DOMNormalizer to validate a xsd against the XMLSchema.xsd

Re: Add schema to xmldocument

or you have to add xmlns=http://sample.com; xmlns:xsi=http://www.w3.org/2001/ XMLSchema-instance to your test.xml. Regards Dick Deneer Op 8-jan-2007, om 23:43 heeft Bernd Kolb (([EMAIL PROTECTED])) het volgende geschreven: Hi, I have a question: I am using xerces 2.9.0. I have a XML

Re: no such method XMLSchemaLoader.loadGrammar(XMLInputSource) ?

I am always using the endorsed arguments -Djava.endorsed.dirs to be sure I get the right xerces. Maybe this helps, DicK Deneer Op 5-dec-2006, om 23:49 heeft ptomsic het volgende geschreven: this problem seems to occur only when i use JDK1.4. i have the following system properties set

Re: Serializing an XSModel to a set of XML Schema documents

I have not seen this in Xerces. But I know the xsd framework from the Eclipse project, see http:// www.eclipse.org/xsd/, has the fucntionality to build a XSModel in memory and serialize it to a xsd. Op 13-nov-2006, om 0:38 heeft Stéphane Mbaye het volgende geschreven: Hello everyone,

Re: XML Schema + Namespace Issues

I think you should then use xsd:schema elementFormDefault=qualified Regards Dick Deneer Op 20-okt-2006, om 7:19 heeft Sean McCauliff het volgende geschreven: I have a schema file where I define two complex types and one of the complex types defines an element with the type of the other complex

SaxParser fails to resolve entity

When using a grammarpool the Saxparser will fail to resolve external entities.As soon as the grammar is cached the problem occurs.For my program it is essential that the grammar is cached because of performance issues.Another, but less important, problem comes when caching is on and you are

Re: SaxParser fails to resolve entity

Indeed, I should have looked first . This describes exactly the same issue. DTD caching becomes rather wortless with this bug. Strange that it is only reported until now Thanx Dick Deneer Op 20-okt-2006, om 19:16 heeft Michael Glavassevich het volgende geschreven: Dick Deneer [EMAIL

Why can 't I set a grammarPool on LSParser

I wonder why I may not  use a grammarPool on the LSParser:Code:import org.apache.xerces.util.XMLGrammarPoolImpl;import org.w3c.dom.DOMError;import org.w3c.dom.DOMErrorHandler;import org.w3c.dom.bootstrap.DOMImplementationRegistry;import org.w3c.dom.ls.DOMImplementationLS;import

Re: How to access XMLResourceIdentifier from LSResourceResolver

Just tested the your suggestion of ExternalSubsetResolver. Thanks, this works great! Op 16-okt-2006, om 23:50 heeft Michael Glavassevich het volgende geschreven: Dick Deneer [EMAIL PROTECTED] wrote on 10/16/2006 05:20:47 PM: As you have probably seen, I created XERCESJ-1204

Re: Dynamic Lookup of Schema Documents

(ValidatorImpl.java:159) at javax.xml.validation.Validator.validate(Validator.java:82) at SchemaTest.main(SchemaTest.java:14) Simon On 25.09.2006, at 23:06, Dick Deneer wrote: Can't you use the LSResourceResolver in combination with the JAXP Validator. Dick Deneer Op 25-sep-2006, om 22:22

Re: Dynamic Lookup of Schema Documents

Can't you use the LSResourceResolver in combination with the JAXP Validator. Dick Deneer Op 25-sep-2006, om 22:22 heeft Simon Raess het volgende geschreven: Hi I'm developing an XML format that is extensible. The format serves as a kind of container with well-defined extension points

Re: Characters divided into 2 parts in Xerces 2.8.0

This is normal behaviour of a SAXParser. See http://xerces.apache.org/xerces2-j/faq-sax.html#faq-2 or  http://www.xml.com/pub/a/2001/12/05/sax2.html for  a explanation. You have to buffer the characters.Op 16-jul-2006, om 18:59 heeft Xaltotun het volgende geschreven: Hi all. My name is Xaltotun. I

Re: Using grammarpool with included schemas

es/java/trunk/src/org/apache/xerces/impl/xs/XSLoaderImpl.java?revision=406145view=markup[2] http://xerces.apache.org/xerces2-j/javadocs/xni/org/apache/xerces/xni/parser/XMLEntityResolver.htmlMichael GlavassevichXML Parser DevelopmentIBM Toronto LabE-mail: [EMAIL PROTECTED]E-mail: [EMAIL PROTECTED]Dick D

Re: Using grammarpool with included schemas

You may be theorically right, but it is obvious that it would be very practical to have it available together with the systemid in the entityResolver. Returning a schema with another namespace is just useless. And in continuing about my question if the parser will resolve the entity by

Re: Using grammarpool with included schemas

7-jul-2006, om 23:08 heeft Michael Glavassevich het volgende geschreven: Dick Deneer [EMAIL PROTECTED] wrote on 07/07/2006 04:00:09 PM: You may be theorically right, but it is obvious that it would be very practical to have it available together with the systemid in the entityResolver

Re: More on schema navigation

().getType()): You wil get a modelgroup or element or wildcard. Dick Deneer Op 29-jun-2006, om 22:54 heeft Wax, Ed het volgende geschreven: I'm attempting to read a schema so that I can ascertain the structure as well as data types of the elements. For complexTypes I can get close but can't quite

elementFormDefault

Hi, I have a XSModel (either through the PSVI after validating a Dom or direct through XSLoader). Now I want to retrieve some values that are normally in the Document element of the schema xml: elementFormDefault, attributeFormDefault and which prefix is bound to a certain namespace. ===

Re: [XML Schema] Invalid constraint value error (bug?)

. A value of zero (or others that are conforming the pattern) is accepted. It seems the default attribute causes the problems. Maybe a developer can confirm this bug? Dick Deneer Using Xerces 2.7.1 I get an error loading the following schema: ?xml version=1.0 ? xs:schema xmlns:xs=http

Re: [XML Schema] Invalid constraint value error (bug?)

Ok, But this is not consistent with the fact that an instance document with a 0 value is valid. Dick Deneer Peter McCracken heeft op woensdag, 4 jan 2006 om 17:32 (Europe/Amsterdam) het volgende geschreven: Stanimir Stamenkov [EMAIL PROTECTED] wrote on 01/04/2006 10:26:07 AM: Seems

Issues with DTDGrammar class

s does not always work. Maybe the String object of the elementName must be exact the same object as stored in the DTDGramar class ???. I had to program a workaround by just looping through all the elementDeclarions (by means of method grammar.getNextElementDeclIndex(i)) Regards Dick Deneer

Re: Current Element Node

etc. The related node always gives null. So may be this is a real bug. You can just run the program to see it yourself. Regards and have a nice ChristMas Dick Deneer Output: Program started Error Attribute to is required and must be specified for element type note. LineNr 1 Node null

Re: Current Element Node

and used a saxparser to report invalid treednodes. The dom revalidation in this last build is much more faster and accurate than my workaround. Thanks again, Dick Deneer Michael Glavassevich heeft op vrijdag, 23 dec 2005 om 18:54 (Europe/Amsterdam) het volgende geschreven: Dick Deneer [EMAIL

GrammarPool and property frustration

? SetParamer/setProperty/setFeature/setAttribute, they all do the same, but slightly different. I think I really need a matrix to know where to set what. Regards, Dick Deneer program output: Program started Before parse Canset grammarpool false Na parse Canset grammarpool true Program ended

Current Element Node

I am trying to get the current elementNode ( by means of the property http://apache.org/xml/properties/dom/current-element-node ) when the domparser reports an error, but I am getting a null node as result. Using xerces 2.71 wiyh JAXP interface. Can I use this property for this situation?

Validation against external DTD other then referenced in XML instance

I am using the DOM level 3 api to build a Dom from an instance XML file without a DocType (DTD). After I have built the Dom I want to revalidate it against an external DTD choosen by the user. But no validation takes place. On the other hand: If the xml has a reference to an external DTD, this

Re: Notification of Document changes during validation (Continued)

and OwnerElement. A fix for this issue would be great. thank for your help Dick Deneer Michael Glavassevich heeft op vrijdag, 28 okt 2005 om 17:25 (Europe/Amsterdam) het volgende geschreven: [EMAIL PROTECTED]> wrote on 10/28/2005 08:35:19 AM: Michael, I alreay had planned to use the JAXP interf

Default inserted attribues and ownerElement

called XMLDonkey. Dick Deneer See this code: /** * Find attributes that were inserted by validator * and notify other components beacuse they must stay * synchronized with the tree. * We are here dealing with the problem that we receive no * mutationEvent for attributes (with default in xsd