"BERVOETS Wim" <[EMAIL PROTECTED]> wrote on 09/14/2006 11:37:34 AM:
> Hi Michael,
>
> Thanks a lot to make this change still in Xerces 2.8.1.
> I've retested today with the new version and I now don't see the (big)
> leaks anymore.
>
> In fact with Jprofiler I do still see some small leak on th
Stanimir Stamenkov <[EMAIL PROTECTED]> wrote on 09/14/2006 04:27:46 AM:
> (I've send the previous incomplete message by accident, sorry.)
>
> /Michael Glavassevich/:
>
> > SAXException [1] is thrown because character encoding errors are fatal
> > errors (as defined by the XML spec) and SAX say
Greetings,
I am using Sun JDK1.4.2_11 w/Xerces 2.8.0 on the Win32 platform.
I have the following sample code which works fine:
...
Source[] xsdSources = ...;
Document xmlDocument = ...;
Schema schema =
SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI).newSchema(xsdSources);
Vali
Ed,
Thanks for your quick reply!
I'm afraid I have not made myself very clear.
You wrote:
> >From the XML Schema spec (
>
http://www.w3.org/TR/2006/WD-xmlschema11-2-20060217/datatypes.html#regex
> s ):
>
> In regular expression languages that are not implicitly anchored
> at the head and
Title: Message
Daniel,
From the XML Schema spec ( http://www.w3.org/TR/2006/WD-xmlschema11-2-20060217/datatypes.html#regexs ):
In regular _expression_
languages that are not implicitly anchored at the head and tail, it is
customary to write the equivalent regular _expression_ as:
Hi,
I am using Xerces-2.8. I have a problem to load the schema file to validate the XML.
The validation worked when I was using an absolute path for the schema location.
parser.setProperty( "http://apache.org/xml/properties/schema/external-schemaLocation", "
http://test.com/web/manag
Hi everyone,
The Xerces-J team is pleased to announce that version 2.8.1 of Xerces-J is
now available. This release fixes several bugs which were present in
Xerces-J 2.8.0. It also includes a few minor enhancements and performance
improvements.
Specifically, the changes introduced in this rel
Hi Michael,
Thanks a lot to make this change still in Xerces 2.8.1.
I've retested today with the new version and I now don't see the (big)
leaks anymore.
In fact with Jprofiler I do still see some small leak on the
LSParser.parse (17KB for 476 parse operations) but that's not due to my
re-use of
Title: Question on Xerves RegEx implementation
Hi all,
I have an XSD schema that I'm trying to validate using Xerces (Java, v 2.8). Xerces complains about errors in the regular _expression_ syntax, which appears to originate in my use of the '$' character in the regexp. From my understandin
(I've send the previous incomplete message by accident, sorry.)
/Michael Glavassevich/:
SAXException [1] is thrown because character encoding errors are fatal
errors (as defined by the XML spec) and SAX says fatal errors are reported
to the application using that exception.
Thanks. I'm now c
/Michael Glavassevich/:
SAXException [1] is thrown because character encoding errors are fatal
errors (as defined by the XML spec) and SAX says fatal errors are reported
to the application using that exception.
Thanks. I'm now clear why encoding errors are reported as
SAXExceptions but again
11 matches
Mail list logo
