469,910 Members | 1,594 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,910 developers. It's quick & easy.

xerces-2j and qualified optional default attributes

Hi,
I have written a schema, specifying attributeFormDefault and
elementFormDefault to be "qualified". If I parse an instance document
validating against this schema with the DOMParser from xerces2-j (2.8.0)
and then serialising the DOM-tree again into a file, all optional attributes
are added with their default values, but they are not qualified with a
namespace-prefix, which finally prevents the serialised document from
being valid with respect to the schema.
How to tell xerces, to qualify the optional attributes with their
namespace when they are added to the DOM-tree?

--
Thanks in advance,
Robert...

Oct 19 '06 #1
2 1272
Robert W. wrote:
I have written a schema, specifying attributeFormDefault and
elementFormDefault to be "qualified". If I parse an instance document
validating against this schema with the DOMParser from xerces2-j (2.8.0)
and then serialising the DOM-tree again into a file, all optional attributes
are added with their default values, but they are not qualified with a
namespace-prefix, which finally prevents the serialised document from
being valid with respect to the schema.
How to tell xerces, to qualify the optional attributes with their
namespace when they are added to the DOM-tree?
How exactly do you serialize the DOM tree? I can think of lots of ways
that might or might not be Xerces specific. If you have problems with
your serialization then show us the code you use to serialize.

--

Martin Honnen
http://JavaScript.FAQTs.com/
Oct 19 '06 #2
On 2006-10-19, Martin Honnen wrote:
How exactly do you serialize the DOM tree? I can think of lots of ways
that might or might not be Xerces specific. If you have problems with
your serialization then show us the code you use to serialize.
Ehm, I tried to reproduce the problem with a simple java-application.
This failed, although the problem persists in a tomcat environment. I
think, I should retry to solve my problem in another NG. However,
thank you.

--

Robert...

Oct 19 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Bekkali Hicham | last post: by
reply views Thread by Waseem | last post: by
reply views Thread by Dale Gerdemann | last post: by
3 posts views Thread by Raphael Tagliani | last post: by
1 post views Thread by Waqarahmed | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.