To whom it may concern,
I'm experiencing some memory leaks. Here are all the details that I can
provide.
* Just by calling XMLPlatformUtils::Initialize() and doing absolutely
no parsing, I'm getting memory leaks when my test program terminates.
* I have attached a text file which cont
Tri,
if you download the xml4j_3_0_1 software, this reference will tell you in
detail
what the differences are:
C:\xml4j\XML4J_3_0_1\docs\html\index.html
Tom
> --
> From: PHAN Tri[SMTP:[EMAIL PROTECTED]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2000 3
[EMAIL PROTECTED] wrote:
> Can you just send your OS/2 files to Jeffrey?
No problem. I just need to finish re-synchronizing everything. Which probably
won't happen until Sunday.
> Did you mail me the OS/2 platform/compiler files?
Nope. I was referring to the diffs I posted last week. I was kind
Hi,
I want to read a DTD
and generate valid XML-File (XML-Document). This is called "validating
generation" in the
book, "XML and Java - Developing Web Applications" by Maruyama, et al.
In the IBM parser (version 2) this is how it begins:
...
// Reads the DTD from the file
String dtdfile = "depa
Cool, thanks for that... I was still using the previous version ( the
XML4J_3_0_0EA3 one ).
So I got the latest version, and tried to build the jar files ( im
running Solaris 2.5.1 ).. and
1) The makefile ( src/Makefile.incl ) is not compatible with sun make
[EMAIL PROTECTED]:/home/richja/li
Tom Locke wrote:
>
> Hi,
>
> Could you forward this request to the guys in charge of the Xalan and Xerces
> downloads:
>
> Could you generate your javadoc with the -use flag - it's a very big API and
> this makes it a lot easier to find your way around.
>
> Thanks,
>
> Tom.
Done :) I'm sendin
There was lots of discussion on this, but not really much of a
conclusion. We're currently using Tidy as a preprocessor for nasty
random HTML pages, but it seems to be overkill. It does lots of stuff so
we get perfect HTML out the other end, rather than just creating
something that's well formed.
[EMAIL PROTECTED] wrote:
>
> I apologise if i've missed this in the docs, but once I have parsed my
> XML doc into a "Document", is there any way thay I can turn it back into
> XML ( say after adding / changing some nodes )...
>
> I'm looking for a Document.toString() or similar
If you're us
I apologise if i've missed this in the docs, but once I have parsed my
XML doc into a "Document", is there any way thay I can turn it back into
XML ( say after adding / changing some nodes )...
I'm looking for a Document.toString() or similar
TIA
Cheers!
James Richardson
"Ralf I. Pfeiffer" wrote:
>
> I agree. It was my proposal. The vote passed overwhelmingly.
>
> Could we get an update on when this split will take place?
Sorry, this dropped of my plate. What is the 'exact' name required and
I'll created it right away.
DW
am a newbie
i find the following xsl (at a tutorial) which is supposed to be
an identity transform... and the output of xalan is not the
identity transform of the input file (ignoring the xml header)
how do i do an identity tranform ??
xml:
Hello
aa
aaa
ab
> In the case where the serializer instance doesn't support
> serializing that node type, it could throw an exception.
Why? I mean, how many serializers do you expect to be able to serialize
an attribute or a text node?
When will you use that functionality?
> processor. And there's nothing that
In addition, the "Configurable" setFeature and setProperty functions
remain the
way to set features, and properties on the DOMParser (and of course the
SAXParser
which naturally implements XMLReader).
[EMAIL PROTECTED] wrote:
> The Configurable functionality has been moved to XMLReader in the SAX
Arkin wrote:
> As for serializing Node that happens to be an Attribute, keep in mind
> that we're trying to define an API used by a lot of serializers. The
> question that should be raised is: would it be trivial for them to
> support it? Would a PDF serializer support that?
Perhaps not but you're
Thanks for your patch. It is Bug#72. We will verify and put it in as
appropriate.
-rip
Vassili Dzuba wrote:
> there is two bugs in bug in UTF8Reader in function skippedString,
> that appears when the string being skipped is shared between two chunks.
> - at line 725, index should be reset to fCur
I agree. It was my proposal. The vote passed overwhelmingly.
Could we get an update on when this split will take place?
Thanks!
--
The Configurable functionality has been moved to XMLReader in the SAX2 (Beta
2) standard.
--
17 matches
Mail list logo
