Title: Message
I was just curious to know if anyone knows
if the issue below has been fixed in the latest XalanC version or with a
specific Solaris patch (since it is really a Solaris problem at the end of the
day).
The issue is a message (square root of
negative number) printed on stde
This is probably a question for the XercesC mailing list, but I am looking
for anyone who can help.
I am using the following XMLPlatformUtils call to write the result of a
XalanC transformation directly to disk.
XMLPlatformUtils::openFileToWrite(utf16FileName);
XMLPlatformUtils::writeBufferToFi
Title: RE: Xalan error/warning messages
Indeed, it is working better with "warn(".
Thanks.
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 20, 2003 3:19 PM
To: xalan-c-users@xml.apache.org
Subject: RE: Xalan error/warning messa
It seems to work quite well, especially for error. I did not find any
warnings, and I found some message.
That will do it for what I need for sure. Thanks.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2003 2:47 PM
To: x
I understand. Thanks.
Are there one or two "well known" functions that are used to emit the error
messages? Something that I could use to do an automatic search in the source
code to find all the messages.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROT
I am trying to gather all the possible fatal, error and warning messages
that Xalan can produce.
I go all the ones from Xerces directly from there NLS xml file
(XMLErrList_EN_US.Xml), but I did not find anything like that for Xalan, or
anything that seems to be a central location fro all the messag
Title: RE: nillable, fixed and default XSD attributes
Thanks for the answer.
I will give it a shot in the Xerces mailing list.
I tried as well with the parser/validator of Microsoft .NET and the behavior is the same. I am probably missing something in the XML Schema spec, but I cannot find it.
I recognize that it is more a pure XML question than a Xalan one, but just
in case someone has a good answer for me.
When looking at the XML Schema specification, if you declare an element with
nillable="true", you cannot use the fixed attribute (which, I guess makes
sense).
I did not find anythin
Thanks for the answer.
I did not look at the Xpath/XSLT 2.0 spec at all and did not know that their
scope exploded.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]
Sent: Friday, December 20, 2002 11:58 AM
To: xalan-c-users@xml.apache.org
Subject:
Those are only working drafts in w3c, and I am not sure when they will be
promoted as official recommendations, but any idea/plan for a support of
XSLT 2.0/Xpath 2.0 in Xalan-C?
Thomas
Title: Merging XML documents
I was wondering if anyone has any experience or references to tools/projects/products that can be used to merge two XML documents.
I did a little bit of research through the web and I just found "basic" stuff (grouping same elements at the same level in the tree
Title: Message
Compiler patch on Solaris fixed the second problem as
well. Life is good :-)
Thanks
again for the help.
Thomas
PS:
Compiler patch is both a compiler and runtime library patch. Both the building
machine and the machine running it needs to be updated (or at least this is wha
Title: RE: Xalan 1.4 weird behavior (may be:-)
Interim release fixed the warning on windows.
Recompilation and test execution on Solaris are in process after compiler patch has been installed. I should be able to confirm if it fixes the Solaris problem tomorrow.
Thomas
-Original Messag
Title: RE: Xalan 1.4 weird behavior (may be:-)
Thanks for the pointers.
I will keep you posted on the results.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 9:03 PM
To: xalan-c-users@xml.apache.org
Subje
Title: RE: Xalan 1.4 weird behavior (may be:-)
First message is on windows, second message is on Solaris :-(
I will test with the interim release for the first message.
For the sun compiler patch, where can I find the information about this patch? As part of the Solaris distribution of Xalan 1
That one might be a long shot (I am far from being convinced that this is a
Xalan 1.4 problem), but just in case.
Since we switched to Xalan 1.4, from time to time we get the following error
messages through our error handler:
Xalan warning (publicId: , systemId: , line: 0, column: 0): An excepti
So it is an absolute (or recommended) behavior for the error handler to
throw an exception to stop the parse?
I was hoping that we could let the parse continue (not throwing an exception
in the error handler) in order to collect all the error messages and just
use a flag to say if any errors occur
Thanks again for the advice.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 03, 2002 4:31 PM
To: xalan-c-users@xml.apache.org
Subject: RE: Xalan 1.4 vs. 1.3 and ICU
Hi Thomas,
I'd say you should either stay with 1.3,
Thanks for the information.
Actually, we are not throwing an exception from the error handler and this
is probably the issue.
In 1.3 it seems that we did not have to (compileStylesheet was still
returning the appropriate success/failure code), but that was may be already
a mistake.
We are going to
I'd like a recommendation from anyone with similar experience if possible.
We are currently using Xalan1.3 without ICU.
We need to integrate ICU (for NLS support) and we decided to upgrade at the
same time to Xalan 1.4.
It seems that this move is not as seamless as one could hope :-) Some of our
p
A quick question in case someone experienced the same problem.
If I configure a XalanTransformer with an error handler and if I compile a
stylesheet, any errors in the stylesheet are reported through the error
handler.
In Xalan 1.3, the return of the compileStylesheet operation was also
different
Title: RE: Memory leaks in STD library
It appears that it is a misuse on our side.
Thanks again for the help.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 26, 2002 4:03 PM
To: xalan-c-users@xml.apache.org
Subject:
Title: Element/attribute namespace qualification
The rules to determine if an xml element must be namespace qualified in an XML document are as follow: when the element was declared you specified form="qualified", or the element was declared globally, or there was no value specified for form
Title: Memory leaks in STD library
We are slowly replacing every usage of istrstream, ostrstream in our code by our own classes as it seems, at least on windows 2000 using VC++ 6.0, that there are very big memory leaks in those classes.
Is it something that anyone else experienced as well or
Title: Message
It is
actually not too bad. As specified by the SAX documentation, the XML 1.0
recommendation is not too bad at listing what is a fatal, an error and a
possible warning.
On the
warning side, they leave it open to the parser most of the time, meaning that a
detailed inspection
Title: RE: SAX ErrorHandler errors
I did check the SAX documentation and I found it not very specific either, that is why I sent the email in the mailing list :-)
But it helps anyway.
Thanks.
Thomas
-Original Message-
From: David N Bertoni/Cambridge/IBM [mailto:[EMAIL PROTECTED
Title: SAX ErrorHandler errors
If I define a SAX ErrorHandler to be used for my XSLT transformation (XSLTTransformer.setErrorHandler), I can trap 3 different kinds of errors: fatal, error and warning.
Is there a documentation somewhere of what is a fatal, error or warning?
A couple of exampl
Title: RE: StreamTransform with Visual C++ .NET
Thanks for the help of everyone.
Everything is working fine now that I built everything using VC++ .NET
Both xerces and xalan compiled fine with VC++ 7.0. Only one problem in ExternalFunction sample in Xalan. The compiler is not able to find the
Title: RE: StreamTransform with Visual C++ .NET
It
might start to work better when rebuilding xalan under .NET completely.
Compilation went through without a problem (a couple of warnings here and there,
that's all).
I am
able to run the StreamTransform example now. But most of the other exa
Title: RE: StreamTransform with Visual C++ .NET
Sorry for the multiple emails. Reply All was just the easy way. I will be more careful.
I am running on Windows 2000 server.
My email was not very clear, I think, that is why I sent a clarification right after. The StreamTransform.exe from the b
Title: RE: StreamTransform with Visual C++ .NET
Sorry,
I just realized that my answer might be a little bit
confusing.
I
initially used the binary distribution of xalan and xerces to write a program of
my own. When I realized that I could not make the stream working, I just took
the Strea
Title: RE: StreamTransform with Visual C++ .NET
I actually did not build xalan or xerces. I used the binary distribution.
May this is what the problem is, but I was hoping that VC++ 6.0 built DLLs are "compatible" with VC++ 7.0 (I am probably too naive on that one).
I can definitely try to re
Title: StreamTransform with Visual C++ .NET
Hi there,
I am trying to make the StreamTransform example (from Xalan-C_1_3-win32.zip) with Visual C++ .NET (VC++ 7.0)
I can compile it fine but when I execute it I get the following error:
Fatal Error at (file , line 1, column 1): The main XML
33 matches
Mail list logo
