> Does the DocumentBuilderFactory (and/or Impl) read properties from a
> specific file? Or, do I have to use a -D on the command line or write my
> own property setting code to override the default property settings? For
> example: the property "javax.xml.parsers.DocumentBuilderFactory"
default
> Any idea of when we might be able to officially look at the ProjectX
> source code under an open source license (the current Sun license makes
> it impossible for me to look at it, since Sun claims to own anything I
> think of after that)?
Given that you work for IBM under which we've got all so
I like option #3. Perhaps even make it so you can flip a switch and
recompile to work with a plain std::string (8-bit chars). If you know that
your documents will all be ASCII, this could be a big memory savings.
But what is it about the current state of the standard libraries that would
be li
A while back there was a discussion about DOMString
and the fact that it uses pointer semantics as opposed
to value semantics. I don't think there was a conclusion.
I can think of three possible solutions:
1. Don't change anything (except maybe add a larger red flag
in the documentation).
So, do you have an advance copy of the next working
draft of XML Schema or participate on the Working
Group? If not, it would seem that everything has to
hold until the next draft (due Dec 16th).
I did post a couple of suggestions on the Schema
(support for lists and multiple lexical patterns for
I'm running XML4J_3.0.0EA3 under OS/2 Warp 4 with the 19991026 1.1.8 JDK. If I
enter the following:
cd d:\xml4j\data
java org.apache.xerces.domx.XGrammarWriter -d personal.xml
I get the following exception:
java.lang.NullPointerException
at
org.apache.xerces.parsers.DOMParser.getFirstChildEl
As a first step, I would like to make available a snapshot
of the repository as a tar ball via the Web page. This tar ball can
be created once / two or three times a day and will be replaced with
new ones the next day. Only an automated solution.
This is not a substitute for stable version release
The Xerces CVS is rapidly getting out of sync with the prebuilt
binaries. I would like to see us establish a regular schedule for
producing pre-built build snapshots that people can use.
At the very least, we need to do a 1.0.1 to fix a few bugs.
I'd like to see us do a pre-built build every wee
Hi,
I've updated the contents of the status file, and I'm posting it so that
people can
see where things stand.
I'm including it below for those who haven't seen it. Please feel free to
tell me if
there are things that should be on the list.
This is the first drop of the Xerces for Java code b
Hi David,
I recently checked in some fixes that provide a solution to this problem.
The fixes allow the parser to react to data as it comes in, instead of in
buffer sized (16K) blocks.
I've attached a source file that shows how to make use of the new
functionality. I'll try to write this up and
What encoding are your files using?
Have you tried a newer JDK?
Ted
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 10, 1999 2:00 AM
Subject: j-xerces under solaris?
> Hi All,
>
> I downloaded the Java xerces source-packages, compiled thes
11 matches
Mail list logo