Someone sent in a small fix for the URL class the other day. I made that
change and checked it in. He then sent a message indicating that other
Apache projects give attributions (in the change log?) for patches, and why
didn't we do it. I'm saying 'he' here because it was sent to a mail account
A +1 here.
Jeffrey Rodriguez
XML Development
IBM Cupertino
From: Ralf Pfeiffer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: separate xerces-dev into xerces-c-dev xerces-j-dev (+1)
Date: Wed, 02 Feb 2000 12:06:33 -0800
Dear xerces-dev community,
I would like to get
Irving Reid <[EMAIL PROTECTED]> notes
> We're building an application in c++ on Linux. We began with the
> Xerces-C 1.0.1 release, but recently switched to the most recent CVS
> version.
>
> On both versions, we are getting warnings from the compiler when we
> turn on strict warnings:
[Problems
I get the following message when building the code from
Xerces-J-src.1.0.1.jar...
javac OutputFormat.java
OutputFormat.java:67: Class org.w3c.dom.html.HTMLDocument not found in import.
import org.w3c.dom.html.HTMLDocument;
^
1 error
make[5]: *** [OutputFormat.class] Error 1
After checking,
+10. Does this mean I can't +1 the next 9 things?
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Ralf Pfeiffer <[EMAIL PROTECTED]> on 02/02/2000 12:06:33 PM
Please respond to [EMAIL PROTECTED]
To: [EM
Ralf Pfeiffer wrote:
>
> Dear xerces-dev community,
>
> I would like to get a quorum of (+1) responses to separate out the
> xerces-dev group into xerces-c-dev, and xerces-j-dev.
>
> We developers of Xerces-J and Xerces-C are having a lot of difficulties
> interpreting the email, and questions
Pier,
Do you know about our SAX2DOM and DOM2SAX adapter beans which is part of the
XPK4J on AlphaWorks (recently deprecated)?
-rip
Pierpaolo Fumagalli wrote:
> [EMAIL PROTECTED] wrote:
> >
> > -0.7
> >
> > I would only state that this will obviously make a difference in
> > performance in large d
Dear xerces-dev community,
I would like to get a quorum of (+1) responses to separate out the
xerces-dev group into xerces-c-dev, and xerces-j-dev.
We developers of Xerces-J and Xerces-C are having a lot of difficulties
interpreting the email, and questions in this group. Many of us have
answered
[EMAIL PROTECTED] wrote:
>
> -0.7
>
> I would only state that this will obviously make a difference in
> performance in large documents, since every trip out of the parser now goes
> through twice as many calls along the way, with both sets being
> indirections via a pointer. For that reason I pe
-0.7
I would only state that this will obviously make a difference in
performance in large documents, since every trip out of the parser now goes
through twice as many calls along the way, with both sets being
indirections via a pointer. For that reason I personally wouldn't be in
favor of gett
Don't be so quick to blame HotSpot here!! This fails with Karen's files on Sun
win32 1.2.2 both classic and HotSpot and also on IBM Win32 1.1.8.
Look at DeferredDocumentImpl.java. When you call binarySearch from line 819,
you're supplying...
values[] = fIdElement = int[128]
start = 0
end = fIdC
> Here is my project. I used it with src_1_0_1, but had to do some code
> changes.
> The Project files are in projects\win32\BCB4\xerces-all, the build is
> parallel to VC. It contains a project group and two projects: xerceslib
> (DLL) and DOMPrint (command line application).
>
> Dietrich
>
Hi
You should dump Hotspot. It has problems running correct Java class
files, that
other VM's (Sun Classic JVM, IBM JVM, etc.) have no trouble running.
At least, that is our experience with Hotspot.
Mike
Karen Schuchardt wrote:
>
> This is in reference to a previous mail under the same subject.
Paul Prescod wrote:
>
> Pierpaolo Fumagalli wrote:
> >
>
> > Since with SAX 2.0 we'll be able to fully build a DOM, what about
> > "dropping" the current DOMParser and SAXParser, keeping just one of them
> > (the SAX one) and relying on a SAX-to-DOM to get the documents?
>
> I strongly support t
We're building an application in c++ on Linux. We began with the
Xerces-C 1.0.1 release, but recently switched to the most recent CVS
version.
On both versions, we are getting warnings from the compiler when we
turn on strict warnings:
g++ -Wall -O -g -c Rule.cpp -o Rule.o
In file included fro
This is in reference to a previous mail under the same subject. Please
refer to it for the full
example.
I am using the vanilla Java 1.2 version (not 1.2.x) and xerces 1.0.1
under Solaris 2.6.
Should I be upgrading to a newer version of java?
Thanks,
karen
Let me take a wild guess... Yo
Pierpaolo Fumagalli wrote:
>
> Since with SAX 2.0 we'll be able to fully build a DOM, what about
> "dropping" the current DOMParser and SAXParser, keeping just one of them
> (the SAX one) and relying on a SAX-to-DOM to get the documents?
I strongly support this idea. It will be useful to be able
I am still having problems to post to this mailing list. So please excuse
me if
this is a duplicate.
We agree to make the following updates to our proposed changes
[1] use "unsigned int" instead of "unsigned long" as Dean Roddey suggested.
[2] change names in FilterAction to those of IDL as Curt
Sorry if you got this twice. I did not see it show up on the archive so I'm
assuming it didn't
make it to the mailing list
Karen
> Hi,
>
> I have a fairly large xml file that makes use of a schema. I get the
> following stack trace
>
> java.lang.ArrayIndexOutOfBoundsException: 128
>
You cant't use VC-build C++ DLLs with C++ Builder (is possible with plain
C). It's not only the library format, it's also because of the different
name mangling. So you have use your own project/library. I set up a project
and got it working. I'm waiting for the next release to test it again and
ch
Andy Clark wrote:
>
> As Mike said, I'm going to be adding support for SAX2beta this
> week. We held up our build and release to get this feature in.
> Expect it "real soon now".
Lovely :) Thank you so much :)
Pier
--
I have an idea...
I already have some classes doing SAX-to-DOM translation, and
I'm currently in the process of bringing them from SAX version 1 to
version 2.
Since with SAX 2.0 we'll be able to fully build a DOM, what about
"dropping" the current DOMParser and SAXParser, keeping just one o
The new NetAccessor API has already been discussed in a previous tech talk.
In 25 words or less, it allows you to plug in a handler for http:// and
ftp:// based XML entities and get them into the parser. You have to
implement the NetAccessor API and a related BinInputStream derivative, and
you c
The Borland header file was fixed, so it should be correct in the
repository now, and it should all compile as is. You do have to build your
own version though, since I don't think you can use the VC++ built DLLs and
Libs directly.
Dean Roddey
Software W
Let me take a wild guess... You are using Java 1.2.2 with HotSpot.
Am I right? A lot of people are reporting erroneous array index
expections because HotSpot is buggy. If you are using HotSpot,
please turn it off and try again. If your problem persists, we'll
take a look at it.
P.S. Always include
If you want to fix it to a 32 bit unsigned, there is already a type defined
in the per-compiler files for that. But, I would argue that its best here
to just used unsigned int and be done with it. On the vast majority of
platforms it would be a 32 bit unsigned. But, on platforms where 64 bit is
Pierpaolo Fumagalli wrote:
> Is anyone interested in supporting SAX2 Beta (the new release that
> just came out)... Do you have any plans?
As Mike said, I'm going to be adding support for SAX2beta this
week. We held up our build and release to get this feature in.
Expect it "real soon now".
--
A
There's a binary drop of solaris 2.6 on alphaworks (www.alphaworks.ibm.com)
but that's with CC compiler version 4.2. So, anyway you have to recompile
the whole code again. I hope you're following the right instructions for
building (with the right switches) as documented.
There was some discussion
There is already a Perl wrapper (Xerces-P I guess its called.) So you don't
have to do any work there. As to the 1.1.0 release, somehow someone got a
little ahead of themselves (hope it wasn't me :-), since that release is
just now about to go to testing. Its in the 'any day now' mode so look fo
We've been trying to use Xerces-C 1.0.1 with Borland C++ Builder 4, and
have run into a problem with xerces-c_1.0.lib included in the
pre-compiled Win32 distribution.
The Borland linker reckons it's not in OMF format, and suggests using
the coff2omf utility to convert it. Unfortunately coff2omf re
Mike Pogue wrote:
>
> I don't know how long it will take, but Andy told me "not too long".
Yep... I thought so... I was about thinking doing it myself if nobody
wanted to do it... They simple "rescrambled" all the methods from
the alpha version in new and better intelligent interfaces...
> Every
I don't know how long it will take, but Andy told me "not too long".
Everybody should be aware that the SAX2 spec is still not final, so it
could
(and probably will) change again.
Mike
Pierpaolo Fumagalli wrote:
>
> Mike Pogue wrote:
> >
> > Yes, SAX2 just updated on Monday (or over last weeke
Mike Pogue wrote:
>
> Yes, SAX2 just updated on Monday (or over last weekend).
> I think Andy Clark is looking at updating to the latest spec right away
> (before the next Big Release).
Wow... That was fast :) Thank you Mike :) I'll ask Assaf to patch the
serializers code too, then we can ship th
Wong Kok Wai wrote:
>
> > Is anyone interested in supporting SAX2 Beta (the new release that
> > just came out)... Do you have any plans?
>
> Are you saying implementation plans?
Yes... what other kind of plans could I be interested in? :) :)
Pier
--
--
Yes, SAX2 just updated on Monday (or over last weekend).
I think Andy Clark is looking at updating to the latest spec right away
(before
the next Big Release).
Mike
Wong Kok Wai wrote:
>
> Are you saying implementation plans?
>
> Pierpaolo Fumagalli wrote:
>
> > Is anyone interested in suppo
I have proposed that we implement an automated build system (Tinderbox)
on the xml.apache.org PMC list.
It's being voted on right now (so far, all +1 votes).
Tinderbox does continuous builds, on many platforms, with results
available and visible to all.
And, it keeps track of when the CVS tree is
Dean Roddey wrote:
The only comment I would add is that I would have picked 'unsigned int'
instead of unsigned long. It would be the most natural value to use when a
particular site is not required. The rest of the code uses unsigned int in
such circumstances, so it would also insure the most inte
I have problems to build the Library on Sparc Solaris 2.7 with the
CC-Compiler v5.0
There is the Error while linking th .so
ld: Schwerer Fehler: Symbol
'RefHashTableOfEnumerator::~RefHashTableOfEnumerator
#Nvariant 1()' ist als erweiterbar definiert:
(Datei ./obj/DTDAttDefList.o and Datei
Hello
We have the idea to use XML to combine application data (e.g. a message
block in SWIFT format) with additional header data that are used for IPC
between two processes of a payment application.
Can you recommend us to use Xerces for this translation step, i.e.
convert a message block to an X
Are you saying implementation plans?
Pierpaolo Fumagalli wrote:
> Is anyone interested in supporting SAX2 Beta (the new release that
> just came out)... Do you have any plans?
>
> Pier
>
Is anyone interested in supporting SAX2 Beta (the new release that
just came out)... Do you have any plans?
Pier
--
- P I E R -
stable structure erected over wat
Christoph Kliemt wrote:
>
> ->"Josh" == Josh Bers <[EMAIL PROTECTED]> writes:
>
> [...]
>
> gpl? (em... err... or is this a
> "ibm-community-i-dont-realy-trust-gpl" license?!) ;)
The Apache license is most definitely *not* GPL -- if it were, you
couldn't use the code without making your soft
[EMAIL PROTECTED] wrote:
> You know that you can always get the most recent working copy of the code
> from the Apache CVS repository, right? So you could get that now and build
> it yourself and get started, then take the official release when it comes
> out.
Yep -- I was doing this with the Lin
John Franey wrote:
> Do the developers of xerces view this as a bug to fix or the
> application of xerces must provide syncrhonization? By the way, for
> my application to provide synchronizisation I need to sync on every
> get* call in the DOM nodes, because all DOM node implementation behave
> i
I, too, wondered why XML4C chose to implement this differently than what is
defined in the DOM level 2 spec.
- Mike
-Original Message-
From: Arnold, Curt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 01, 2000 5:49 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Proposed Xerces-C API Changes
You are right. Current names of FilterAction value do not match those in
the IDL.
We will make the changes as you suggested. Thanks.
Chih-Hsiang Chou
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
- Original Message -
From: "Arnold, Curt" <[EMAIL PROTECTED]>
To: <[EM
Mike,
This looks like a real problem. I'm looking into it.
Thanks for notifying.
Arudhati
- Original Message -
From: KRAUSE,MIKE (HP-FtCollins,ex1)
To: [EMAIL PROTECTED]
Sent: Friday, January 28, 2000 6:17 PM
Subject: Using DOM_NodeIterator
Hi,
I'm trying to use the DOM Level 2 DOM_No
You are right. We will make that name changes.
Chih-Hsiang Chou
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
- Original Message -
From: "Arnold, Curt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 01, 2000 4:49 PM
Subject: RE: Proposed Xerces-C
I've got a few changes for XSchemaValidator.java that add to its usability:
Add 2 methods (addInternalEntityDecl(), addExternalEntityDecl()) that do just
what they imply. There's really no other way to have a parser extension declare
entities and still validate against a schema. Both already exi
Why aren't the values for FilterAction: FILTER_ACCEPT, FILTER_REJECT and
FILTER_SKIP? That would be consistent with your treatment of ShowType.
The only comment I would add is that I would have picked 'unsigned int'
instead of unsigned long. It would be the most natural value to use when a
particular site is not required. The rest of the code uses unsigned int in
such circumstances, so it would also insure the most interoperability
with
51 matches
Mail list logo
