Joseph Kesselman/CAM/Lotus wrote:
>
> But there is a backward-compatability concern if folks have code which
> relies on the old behavior, so a large part of the question is how many
> users will be affected and how badly.
That's indeed what we're trying to assess. Specifically we'd like to
hear
Hello! I'm new to the list so forgive me if this has been asked before. I
attempted to search the archives, but I had trouble finding them.
Anyway...
I recently downloaded Xerces-J-bin.2.0.1.zip (as in a couple of days ago)
and unpacked it on my Windows laptop. The top level document file in
docs
Title: pattern in schema
we
just found that Xerces 1.4.4 support XML schema 1.0, which does not support
{n,m} pattern. and "^\d{1,9}\.\d{2}$"
does
not work either. have to change it to "\d\d*.\d{2}" plus a maxLength
restriction.
but
thanks any way, Chris.
James
-Original Messag
Hi,
> Yes. The difference is that (a) the DOM-builder would have to take
> responsibility for doing this a bit more explicitly (or calling
> normalizeDocument when it's done -- which is probably a less efficient
> option),
yes we should make it clear when these defaulting and whitespace normalizi
> don't the defaults also get set when the parser performs a validating
> parse() on the incoming document?
Yes. The difference is that (a) the DOM-builder would have to take
responsibility for doing this a bit more explicitly (or calling
normalizeDocument when it's done -- which is probably a le
Hi
don't the defaults also get set when the parser performs a validating
parse() on
the imcomming document?
Cheers
David
- Original Message -
From: "Elena Litani" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Wednesday, March 20, 2002 1:16 PM
Subject: DOM L2/L3 default attrib
Title: pattern in schema
Hi James,
Just from experience with regexes,
it might need to be "^\d{1,9}\.\d{2}$", specifying the start and end of the
string. Otherwise, if it finds the pattern at all, it will match (e.g.
1234567890.12 = 1(234567890.12), which is a match but not what y
Title: pattern in schema
Hi,
I have the following definition in schema:
shouldn't 1234567890.12 be invalid value for this type? but Xerces 1.4.4 does not catch it. Anyone knows why?
thanks in advance,
Jame
thanx for the link Elena, i have used the jar files dated 20-Mar-2002 and
now
the behaviour is different, there are no more comments of the DTD merged
into
the output XML of the serializer.
cheers, Peter
> -Ursprüngliche Nachricht-
> Von: Elena Litani [mailto:[EMAIL PROTECTED]
> Gesendet:
thanks for this information. i do not dig CVS ?! please help.
b.t.w. i bought your book a while ago and i like it very much.
Peter
> -Ursprüngliche Nachricht-
> Von: Elliotte Rusty Harold [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 21. März 2002 16:18
> An: [EMAIL PROTECTED]
> Betre
Elliotte Rusty Harold wrote:
> I don't
> think the Xerces folks make nightly builds available, though if I'm
> wrong perhaps someone could point me at the right URL?
The nightly build -
http://gump.covalent.net/jars/latest/xml-xerces2/
--
Elena Litani / IBM Toronto
--
Hallo,
I am working on a project using XML as the query
language. To process the query, I need to validate
the query, which is a xml file, against a specified
XML Schema, then transform the element in the query
into interne presentation. I would like to know
whether I can get the type informatio
Hi folks,
Noticing the recent flurry of queries and bug reports concerning Xerces
support of aspects of schema identity constraints, I thought it would be
useful to let the community know that this stuff is going to be revisited
very soon. Identity constraint validation is about the only portion
Hi all,
i am using xerces 2.0.1 for validating xml against a dtd and afterwards
manipulating the dom tree.
When i use the serializer, all my comments from within the DTD appear in the
output xml. Is there
a way to avoid this?
I just posted a bug on this yesterday and was told it had been fixed
in
Hi all,
i am using xerces 2.0.1 for validating xml against a dtd and afterwards
manipulating the dom tree.
When i use the serializer, all my comments from within the DTD appear in the
output xml. Is there
a way to avoid this?
With xerces 2.0.1 the functions getFeaturesRecognized() as well as
getP
Hi!
I executed 'ASBuilder' sample in xerces 2.0.1.
But I get ClassCastException. This run time exception took place at below:
// get DOM implementation
DOMImplementationAS domImpl =
(DOMImplementationAS)DOMImplementationImpl.getDOMImplementation();
I executed it under Linux. But
Hi Sridhar
I tried this. I get the same error, except that the "must match" string
includes "{0-1}" on the end to indicate the choice is optional.
Do you think this is a bug in Xerces?
regards
Mark
-Original Message-
From: Sridhar Raju Y [mailto:[EMAIL PROTECTED]
Sent: 21 March 2002 05
I'm having a problem getting one aspect of my schema to work with xerces.
Simply put, there is an element in my schema like this:
Eddie Robertsson wrote:
> I posted this bug report in Bugzilla a couple of weeks ago (for version
> 2.0.0) and I never got a reply. Today I realized that the bug still
> appears in 2.0.1 so is anyone else experiencing the same thing?
Using the code you gave, I don't see an out of memory
exception
Hi all,
I posted this bug report in Bugzilla a couple of weeks ago (for version
2.0.0) and I never got a reply. Today I realized that the bug still
appears in 2.0.1 so is anyone else experiencing the same thing?
I'm getting an OutOfMemoryError when parsing
Hi Mark,
Then you are right. It should not throw any error.
Change your schema
This code may help you.
regards,
Sridhar
-Original Message-
From: Mark Lines-Davies [mailto:[EMAIL PR
I seem to recall that sandy gao had stated that the 'plumbing' was already
in xerces-2 to make viewing an ASModel possible, but that it has no API
because the API hadnt been designed yet.
if that's true, could we just have a lame API? we can try it and figure
out what works, right?
call it itera
22 matches
Mail list logo
