Karen Schuchardt wrote:
> Is this something that is just not currently implemented or am I
> confused?
You are not confused. This is a limitation of our current
XML Schema support.
> If this is just not currently supported, does anybody have plans to work
> on it.
We do have plans to work on it
Defaulting fNamespacesEnabled to 'true' in XMLParser causes namespaces to be
enabled for DOMParser as well as SAXParser. This causes Schema validation
(which uses the DOMParser) to choke with "Attribute "xmlns" must be declared for
element..." plus a "must be declared" error for every element and
Thanks for the bug report. I filed a defect a checked in a fix for
importNode.
--
Arnaud Le Hors - IBM Cupertino, XML Technology Group
What version of gmake were you using? I did try on solaris 2.7 and gmake 3.76.1
and it worked fine.
Arundhati
Michael Hucka wrote:
> Pardon me if this is the wrong place to send reports of this nature.
>
> I've been trying to build Xerces 1.0.3 on a Solaris 2.7 box using GNU make,
> and ran into
This clearly shows that the source library build infact failed. Even if there
is failure diuring compilation the build continues. So, you probably need to
redirect to a log file while building and check the log for failures. The most
key thing is to set the XERCESCROOT and library path environment
+1
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
"Chih-Hsiang Chou" <[EMAIL PROTECTED]> on 03/08/2000 06:17:11 PM
Please respond to [EMAIL PROTECTED]
To: "xerces-dev" <[EMAIL PROTECTED]>
cc:
Subject:
At this point we would probably only be interested in those mods for the
new 1.1.0 base. Perhaps some other foks might want to have access to your
work for the 1.0.1 stuff, but we are now up to 1.1.0 and would want to
check in projects against that. In fact, I think we have checked in some
new p
It appears that I will have to modify most of the derived classes
shipped with Xerces-C. I have tried
building the programs in the tests directory to see if the library
works. Unfortunately, my compiler (gcc version 2.95.2) complains about
constructing objects of classes that are derived from the
Hello all,
I'm new to the list, so please forgive me if I say or ask something
stupid...
* I'm using Xerces 1.0.1 for my project. My project builds on the Mac using
Metrowerks CodeWarrior Pro 5.3 and Windows using CodeWarrior and VC++. The
CodeWarrior projects included with the Xerces distribut
I have made progress. I built and installed gcc 2.95.2 on the solaris
2.6 machine and built the xerces-c libraries. The build appeared
successful, so I tried building the samples. None of the samples will
build - I get "Symbol referencing errors" with undefined symbols first
referenced in the li
hi,
xsl parser for java seems to be slow ?. it's much noticable when i
used it to traslate
5+ documents ,it take time to load VM again and again .Do you have any xsl
parsers in c++ ,
or can suggest an alternative
we could had a round about way if xsl parser for java were able to handle
multipl
On Wed, 8 Mar 2000 10:54:07 -0800, James Fowler wrote:
>architecture. It is also sometimes a little top-heavy in implementation.
>For raw, low level "byte" oriented I/O, it is sometimes better to use a
>simpler class as described above, and then optionally wrap an ostream around
>it where the for
Jeff Lewis wrote:
> We are having an internal discussion about whether or not to trust the
> ordering of elements within the DOM once an XML document has been parsed.
>
> I am arguing that the DOM should retain the order of elements from the XML
> file, but I have yet to find any requirement, W3
Yes, I was able to verify both defects against 1.0.3:
1) In org.apache.xerces.dom.ElementImpl.setAttributeNS(), doc defect where
localName should really be qualifiedName.
2) We seem to be missing code in
org.apache.xerces.dom.DocumentImpl.importNode() to deal with ElementNSImpl
and AttrNSImpl N
Pardon me if this is the wrong place to send reports of this nature.
I've been trying to build Xerces 1.0.3 on a Solaris 2.7 box using GNU make,
and ran into trouble with the Makefile.incl. The problem was that make would
generate an error when the recursive makefiles would finally reach a termin
A couple of bugs in the newly released 1.0.3 (but neither are
regressions).
First, a doc bug:
In org.apache.xerces.dom.ElementImpl.setAttributeNS(), the second
String parameter is named and doc'd as a local name, but is in fact a
qualified name. This is correctly doc'd on org.w3c.dom.Element.
An
To continue on improving Xerces-C, we are proposing the following API
changes. Please post your comments/suggestions here by Mar. 10 (Friday)
4PM. If your applications call any of these API, please update your code as
well.
[1] The following IDL attributes are readonly but have a set method
deca
Your observations are quite correct but I want to point out
that the SAX2 code currently in Xerces is the exact code released by
David Meggison, the author of SAX2 ( SAX2.0beta2 release).
Furthermore the SAX2 beta documentation seems not to be consistant
about the behavior of two parser methods in
Hi everyone.
I wrote:
> Hacked parser still access www.w3.org, when I feed UTF-16 input.
> # try utf-16le.xml & utf-16be.xml in samples.zip.
>
> And hacked parser can't parse some UTF-8 input which can be
> parsed by normal SAXParser.
> # try diary.xhtml (written in Japane
Yes. It is an open source product, so it can be used in commercial products
without any fee. If you want a guaranteed level of support, IBM can provide
that to you for a cost (as perhaps can others.)
Dean Roddey
Software Weenie
IBM Center for Java Techno
Hi I have a question about the state of the schema implementation in
xerces-J 1.0.2
My understanding of the xml schema spec and namespaces is that my xml
document should look
like this:
...
...
However I notice that the example personal-schema.xml looks more like
...
ie. only a defau
Xerces-J 1.0.3 is now available! You can download the binary and/or
source package distributions from the following URL:
http://xml.apache.org/dist/
This time we have also included tar-balls for the unix world.
This release contains the following changes/features:
26: Schema lookup disabled w
There is one thing in the DOM (level 1.0) spec which is relevant,
the description of the method getElementsByTagName for the Element class:
getElementsByTagName
Returns a NodeList of all the Elements with a given tag name
in the order in which they would be encounter
23 matches
Mail list logo
