Michael Gratton wrote:
> I tested it against Xerces-J 1.0.3 and 1.0.2 which both failed to output
> the children and against 1.0.1 which seemed to work fine, but not
> against the CVS version.
Okay, now I'm able to duplicate it. I *never* use NodeList to
iterate over the children because it is inh
I believe I saw something in recent archives about the RevalidatingDOMParser
is broken and will stay broken until the XML Schema is implemented.
Chris
Eric SCHAEFFER wrote:
>
> Hi,
>
> I use Xerces J 1.0.2 and try to validate a document with a DTD :
>
> DTD :
>
>
>
>
> name CDATA #REQUIR
Thanks. I'll fix that. One can never be too pedantic in software, right?
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Igor Tandetnik <[EMAIL PROTECTED]> on 03/15/2000 09:47:34 AM
Please respond to [EMA
As pointed out by Jeff, the defect was:
to replace the line
sa.sin_port = pno;
with
sa.sin_port = htons(pno);
His explanation of this was:
Because multiple byte quantities are needed as part of the TCP/IP
protocol, the protocol designers adopted a single standard for how
multibyte value
Hello,
I read a xml-document with the SAX-interface of the Xerces-J 1.0.3
package. I wrote my own DeclHandler and in this interface I rewrite the
function elementDecl(String name,String model). If the parse reaches the
following line in my xml-dtd
^^
It works . . . thanks a bunch . . .
Peet
- Original Message -
From: "Jeffrey Rodriguez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 15, 2000 6:25 PM
Subject: Re: replaceChild
> Mr. Sneekes,
>
> No your interpretation about [#document: null] and dom.toString() is
Thanks much Jeff.
In retrospect, it feels like, "its so obvious, what the problem was.
Its been staring at you all this time. You just have not been noticing".
Thank you again,
rahul
Thanks. I missed the recursive mutex part. That should fix the
problem.
Thanks again,
Steve
On Mar 15, 11:21am, [EMAIL PROTECTED] wrote:
> Subject: Re: Deadlock
>
>
>
> No, you can't remove that lock. The lock in the get method is to
> synchronize the lazy eval of the message loader. The lock
That all sounds reasonable. How about this. Mail me directly with a list of
the exact errors you got and where. I'll look at those and we'll see what
we can do. We definitely don't want to start putting in conditional code
per environment. But, the other stuff I'll see what I can do to clean tho
Does anyone have code sample using Schemas with Xerces? Do I have to have
anything to set up the parser for it to work? I am getting errors that
indicate the parser can't find any schema or DTD information at all (parser
complains that the first attribute must be declared for the root element
reg
No, you can't remove that lock. The lock in the get method is to
synchronize the lazy eval of the message loader. The lock in the other call
is to synchronize the loading of message text.
And, even if you could get away with it there you'd still have problems
down the line because our platform
- Original Message -
From: Jeff Lewis <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 15, 2000 6:58 PM
Subject: RE: DOM validation
> According to your dtd, 'territoire' is '#REQUIRED' to have an attribute
> 'name'...
>
>
And that's the problem : Xerces tells me the doc
According to your dtd, 'territoire' is '#REQUIRED' to have an attribute
'name'...
-Original Message-
From: Eric SCHAEFFER [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2000 10:56 AM
To: [EMAIL PROTECTED]
Subject: DOM validation
Hi,
I use Xerces J 1.0.2 and try to validate a doc
Hi,
I use Xerces J 1.0.2 and try to validate a document with a DTD :
DTD :
XML document :
http://localhost/dtd/territoire_posterscan.dtd";>
The document seems to be valid (???).
I tried the DOMparser and RevalidatingDOMParser
Eric.
___
Eric
Hello.
I have Xerces-C version 1.1.0
There is the table
static const XMLUInt32 gUTFOffsets[6] =
{
0, 0x3080, 0xE2080, 0x3C82080, 0xFA082080, 0x82022080
};
in util/XMLUTF8Transcoder.cpp. The numbers in this table should have been equal
to the following:
0
(0xC0 << 6) + 0x80
(((0xE0 << 6) +
Mr. Sneekes,
No your interpretation about [#document: null] and dom.toString() is not
exactly correct.
The implementation of toString is as follows:
public String toString() {
return "["+getNodeName()+": "+getNodeValue()+"]";
}
According to the DOM1 specification the following are th
Hi Jeffrey,
I thought this would work, but both (parent) Documents seems to be
[#document: null] if I do Document dom.toString(). And if I look in the
Xerces 1.0.2 code this check is made before replaceChild() can be done. Is
this a bug of the Xerces DomParser?
What to do?
Cheers,
Peet
New co
Peet Sneekes wrote:
>
> Hi,
>
> I want to replace an Element of a Document with another Element from another
> Document.
> So I first clone the new Element and than I do replaceChild() (see sample
> code).
>
> Still it gives the "DOM005 Wrong document" error.
The new child is from a different d
Andy Clark wrote:
>
> Michael Gratton wrote:
> > After parsing an XML document and performing a cloneNode(true) on the
> > resulting org.w3c.dom.Document object, I get a clone of the DOM tree, as
> > I'd expect. However, if I then do a getChildNodes() to any node in the
> > tree, it seems that the
I e-mailed to the xerces-dev group but I think my mail got returned.
So here I go again,
Rahul replace the following line
sa.sin_port = pno;
With:
sa.sin_port = htons( pno);
My explanation follows:
The reason your original source would not work in Linux or the
Free BSD is because TCP/IP manda
>Is anybody actively working on the SGI irix port? I beat the
>Makefiles into submission, and updated the PlatformUtils file.
>It works, but there are still kinks to be worked out. I am happy
>to contribute but do not want to duplicate someone else's effort.
>
>Is anybody else out there workin
Hi,
I have a problem using the new xerces xml Parser ( Version 1_0_3 ).
Perhaps you could help me.
I used the following code :
RevalidatingDOMParser parser = new RevalidatingDOMParser();
parser.setFeature("http://xml.org/sax/features/validation";,
true);
Hi,
I want to replace an Element of a Document with another Element from another
Document.
So I first clone the new Element and than I do replaceChild() (see sample
code).
Still it gives the "DOM005 Wrong document" error.
Any suggestions? Thanks!
Peet Sneekes,
Mediamatic IP,
Amsterdam
sampleC
Hello,
I use Xerces J 1.0.1 (not the last version, I know, but it shouldn't make
differences), and want to create an XML document "on the fly" and to
validate it with a DTD. But it doesn't work
:-(
If I construct my document by programmation, I can't tell the document that
it is finished (and tha
[EMAIL PROTECTED] wrote:
>
> That should work. Are you sure you are using the correct import library,
> have all the library paths set up to point to the right version, etc...?
Oops -- boo boo on my part. I'd adjusted one of my makefiles to use the
1_1 library but not the other.
Now I'm getting
>>Before submitting the changes, how about just giving everyone a discussion
>>of what was required to make it work. This would give us a chance to
>>comment on what you've done and, if we feel something needs to be changed
>>before accepting it, that you can make those changes and test them out
>>
I am experiencing a deadlock in some of the sample programs when I turn
on -v. It happens when this section of XMLValidator.cpp (line 154 in 1.1.0)
gets called:
XMLMutexLock lockInit(&gValidatorMutex());
if (!getMsgLoader().loadMsg(toEmit, errText, maxChars, text1,
text2,
Is anybody actively working on the SGI irix port? I beat the
Makefiles into submission, and updated the PlatformUtils file.
It works, but there are still kinks to be worked out. I am happy
to contribute but do not want to duplicate someone else's effort.
Is anybody else out there working on an S
You don't mention what server you're using to test RedHat. Perhaps the
problem with FreeBSD is related to how locus.apache.org is configured? I
would imagine that TCP/IP port security is pretty tight on the Apache
server.
Dave
Hi,
I am stuck with this problem and would appreciate if anyone had
any suggestions / ideas / theory explaining the behviour that
I describe below.
The problem has nothing to do with XML, but I wish to add
capability to fetch HTTP URL's to Xerces-C. Hence, I am posting
on this mailing list, with
[EMAIL PROTECTED] wrote:
> I have an inconcistency or a bug. With JDK 1.1.7p (VisualAge for Java 3.0)
> XML4J 3.0.0, and LotusXSL 0.19.2, this works, but with XML4J 3.0.0 and
> LotusXSL 0.20.0 I have problems. It doesn't look like an XSL problem, but
> the bug appears with changes to XSL.
You ha
Michael Gratton wrote:
> After parsing an XML document and performing a cloneNode(true) on the
> resulting org.w3c.dom.Document object, I get a clone of the DOM tree, as
> I'd expect. However, if I then do a getChildNodes() to any node in the
> tree, it seems that the Node's children are completely
32 matches
Mail list logo
