Andy Clark wrote:
>
> Pierpaolo Fumagalli wrote:
> > I've seen in the original SAX2 file I got that DocumentHandler has
> > been deprecated, while the one coming with Xerces, in CVS, right now
> > is not?
>
> Actually, the DocumentHandler in Xerces is also deprecated.
> The SAX2beta people deprec
Kenneth Ramirez wrote:
> I just downloaded the latest source code (Xerces Version 1.0, which I had
> XML4J
> Version 3.0 before) and the XMLSerializer class is no longer there?
Version 1.0 is not the most recent release -- 1.0.1 is. Also,
the serializers are being added into the upcoming release.
Ken,
It's definitely in Xerces 1.0.1 (xerces.jar). The class is
org.apache.xml.serialize.XMLSerializer.
Hope this helps,
Jim O'Neill
Ducat Commerce, LLC
http://ducatcommerce.com
-Original Message-
From: Kenneth Ramirez <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date:
I just downloaded the latest source code (Xerces Version 1.0, which I had XML4J
Version 3.0 before) and the XMLSerializer class is no longer there?
Ken R.
could a list administrator please blast this guy away... I'm tired of seeing
every other message "Unsubscribe me". We have already tried to tell this
guy the proper way to unsubscribe, be he just will not relent!!!
- Greg
-Original Message-
From: Paul Pitt [mailto:[EMAIL PROTECTED]
Sent:
This is a known bug in xerces 1.0.1 and has been fixed.
You can get the fix from CVS (copy and paste the code of
the 2nd constructor in DocumentImpl.cpp) or wait for the
upcoming new release.
Chih-Hsiang Chou
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
- Original Message
Ahh, it looks like your version had the changes in a different location in
the file. The resulting merge left both your changes and mine in the file,
so the diff still looked the same. Sorry about that!
Dave
Arundhati Bhowmick <[EMAIL PROTECTED]> on 02/09/2000 04:26:13 PM
Please respond t
The very, very latest source code from CVS (caveat emptor) is always available
at:
http://xml.apache.org/from-cvs/
Distributions (more stable and tested) are available at:
http://xml.apache.org/dist/
Checkout the webpages at http://xml.apache.org for much, much more information
I did that yesterday evening. Do you still see that problem after updating all
the project files?
Arundhati
David_N_Bertoni@lotus.com wrote:
> These changes have still not been checked in. as far is I can tell. Should
> I commit them myself?
>
> Dave Bertoni
>
> [EMAIL PROTECTED] on 02/08/2000
Well, I downloaded the XML parser from IBM's site (XML4J version 3). Of course,
the documentation states that IBM has transferred the code over to Apache and it
is now named Xerces. Is there a more recent version?
Ken Ramirez
"KRAUSE,MIKE (HP-FtCollins,ex1)" wrote:
>
> Hi,
>
> Just a comment to add to this discussion... I don't think the DOM spec
> requires case insensitive compares of strings, but it would be nice if there
> were a way of doing case insensitive compares without having to do a
> translation to a char
These changes have still not been checked in. as far is I can tell. Should
I commit them myself?
Dave Bertoni
[EMAIL PROTECTED] on 02/08/2000 02:02:28 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:(bcc: David N Bertoni/CAM/Lotus)
Subject: Re: XercesLib.dsp proble
You're doing good...you just haven't completed all of the phases necessary
for getting yourself removed from the list. You've successfully sent five
messages asking to be unsubscribed to a global list of users who can't do
anything about your problem...that completes phase one. For phase two, you
Hi,
Just a comment to add to this discussion... I don't think the DOM spec
requires case insensitive compares of strings, but it would be nice if there
were a way of doing case insensitive compares without having to do a
translation to a char * (using transcode) and then doing a strcmpi on the
st
- Original Message -
From: Paul Pitt <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 09, 2000 11:13 AM
Subject: Re: Unsubscribe me
> it did not work again
>
> - Original Message -
> From: Paul Pitt <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: We
- Original Message -
From: Paul Pitt
To: [EMAIL PROTECTED]
Sent: Wednesday, February 09, 2000 9:40 AM
Subject: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
unsubscribe me
Fred,
Linux work is certainly appreciated. We have someone who has already
committed to providing a Linux patch (Jason Stewart). You can send me
your patch and I'll check it out. I would prefer to serialize this
after the patch I am expecting from Jason (provided it happens soon).
Please also
That'll work!
-tom
Gregory Krasnow wrote:
>
> I think I figured this out already...
>
> a) create a StringReader
> b) create and InputSource from the reader
> c) pass the InputSource to parser.parse()
>
> - Greg
>
> -Original Message-
> From: Gregory Krasnow [mailto:[EMAIL PROTECTED]
You're looking at very very old code. The new code doesn't have the init
method, and it will check if encoding is null when creating the
OutputStreamWriter.
arkin
Kenneth Ramirez wrote:
>
> I couldn't call it in the way that you specified, but I was able to call it
> this
> way:
>
>
it did not work again
- Original Message -
From: Paul Pitt <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 09, 2000 9:27 AM
Subject: Re: Unsubscribe me
> if you find out how to get "unsubscribed... plze tell me. I have been
> trying for months and putting "
Jim O'Neill wrote:
> Try the following code.
>
> ByteArrayOutputStream bao=new ByteArrayOutputStream();
> XMLSerializer s = new XMLSerializer();
> s.setOutputByteStream(bao);
> s.serialize(fDocument);// fDocument is xml document
> System.out.println(bao.toString());
I would sugges
Sven Reimers wrote:
> 1. using gmake:
> fails: There is class in src/org/xml/sax/Makefile
> named Configurable - this is not in the source tree
Good catch! Thanks. It's now fixed.
--
Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
Thanks guys for taking on these ports. Once you get them happy, definitely
send them to us so that we can include them in the next drop, assuming that
you want to share the fruits of your labor of course.
Dean Roddey
Software Weenie
IBM Center for Java T
Are you saying you think that the *spec* says it shouldn't be case
sensitive or that you don't think it should? If the spec says it shouldn't
then clearly it shouldn't. But, otherwise XML is pretty much completely
case sensitive and I wouldn't see any reason why this particular API should
be any
Pierpaolo Fumagalli wrote:
> I've seen in the original SAX2 file I got that DocumentHandler has
> been deprecated, while the one coming with Xerces, in CVS, right now
> is not?
Actually, the DocumentHandler in Xerces is also deprecated.
The SAX2beta people deprecated a lot of the original SAX
stu
I don't know for sure if this is the problem or not, but many encodings
supported by
Sun and IBM's JDK's are NOT supported by MS-J++. An exception (just like
that one) is generally thrown when an unimplemented encoding is specified.
It does seem like you might be hitting this problem. If so, it
Harmon,
I'm not sure that I want to degug your code ... at least not until we
have reason to believe their is a bug on our end ... but I can give you
some pointers. First, I have used SWIG extensively to wrap the Xerces
C++ DOM in order to create the Xerces Perl DOM project. It works. You
might
I couldn't call it in the way that you specified, but I was able to call it this
way:
ByteArrayOutputStream bao = new ByteArrayOutputStream();
XMLSerializer s = new XMLSerializer();
s.serialize(doc, bao, null);
return bao.toString();
I think I figured this out already...
a) create a StringReader
b) create and InputSource from the reader
c) pass the InputSource to parser.parse()
- Greg
-Original Message-
From: Gregory Krasnow [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2000 9:26 AM
To: Xerces Developer Lis
Please see http://xml.apache.org/mail.html and search for the "Unsubscribe"
link next to the mailing list you want to get off of. For the
browser-challenged, the link is:
mailto:[EMAIL PROTECTED]
This also tends to work for other mailing lists, apache or otherwise.
Generally sending an email
unsubscribe me
Go to http://xml.apache.org/mail.html, and click on UNSUBSCRIBE!
Mike
Paul Pitt wrote:
>
> if you find out how to get "unsubscribed... plze tell me. I have been
> trying for months and putting "block sender" on thousands of people.. I
> have written and tried and beggeed and pleaded and ev
if you find out how to get "unsubscribed... plze tell me. I have been
trying for months and putting "block sender" on thousands of people.. I
have written and tried and beggeed and pleaded and even prayed to the
digital god. I cannot finger out how to get off this damned XML net
- Origi
In the old IBM xml4j I was able to create a TXDocument from from a string by
creating a StringReader and from the String and then passing this to the
parser.readStream(). I do not seem to find an equivalent method in
XMLParser. Is there an equivalent way to do this?
- Greg
Gregory Krasnow
Sen
XML is, in general, case-sensitive.
See the excellent comments in the Annotated spec on this topic (excerpted here):
http://www.xml.com/axml/notes/CaseSensitive.html
The whole annotated spec (which I encourage everybody to read) is at:
http://www.xml.com/axml/axml.html
In the
That's exactly where I got the basis for my function. Do you see the need for a
function like this, or am I completely off the wall here?
Ken Ramirez
Try the following code.
ByteArrayOutputStream bao=new ByteArrayOutputStream();
XMLSerializer s = new XMLSerializer();
s.setOutputByteStream(bao);
s.serialize(fDocument);// fDocument is xml document
System.out.println(bao.toString());
Jim O'Neill
Ducat Commerce, LLC
www.ducatcommer
[EMAIL PROTECTED] wrote:
> I'll be doing Mac right after I get my build out to my client.
Ah! Great! (One item off my to-do list. ;-)
Were you planning on targetting Carbon?
--Bill
Actually, if you're using or overwise want to download the Xerces-C
distribution, there is a program in the "samples" directory called
"DOMPrint.cpp" that is exactly like your program below. Guess there isn't
anything like it currently built into Xerces...
-- HSN
On Wed, 9 Feb 2000, Kenneth Ram
Hi,
found solution to 2.
Just change src/main/org/apache/tools/ant/task??/Javadoc.java
to give more memory to java job: -Xmx???. There is a line
b.append("java "); Change this!
Sven
Sven Reimers wrote:
>
> Hi,
>
> I checked out the HEAD from CVS
> and tried to
> build Xerces from the sources.
Element.getAttribute(String name) in Xerces 1.0.1 requires that name is
provided
case-sensitive ie as it it saved in th e XML file, but I think that the
implementation should
be NOT case-sensitive!
I convinced the organization that I'm currently consulting to start using Xerces
in our middle tier to return data retrieved from the database to the browser.
We actually have to first go through an ASP page before hitting the browser
(since the site is managed with IIS). In order to return the
Unsubscribe me
Hi,
I checked out the HEAD from CVS
and tried to
build Xerces from the sources.
1. using gmake:
fails: There is class in src/org/xml/sax/Makefile
named Configurable - this is not in the source tree
2. using ant:
works like a charm (at least compiling)
b
> I know we have had a side discussion regarding your contribution of
> patch to put Xerces Perl on Linux (thanks much!). Also, I will test
and
> release an update to Xerces Perl to ensure compatibility with Xerces C
> when the next version is posted, hopefully later this week. If you
get
> me
Unsubscribe me
Pierpaolo Fumagalli wrote:
>
> Another thing.. Why the setLexicalHandler() in SAXParser is protected?
Sorry... Next time I'll look @ the API documentation (setProperty!)
Pier
--
- P I
Pierpaolo Fumagalli wrote:
>
> I've seen in the original SAX2 file I got that DocumentHandler has
> been deprecated, while the one coming with Xerces, in CVS, right now
> is not?
> Is this a willing thing or just a forgotten thing?
Another thing.. Why the setLexicalHandler() in SAXParser is prote
On Tue, 8 Feb 2000, Dudley Irish wrote:
> I have just started trying to port an application to HP/UX. We had
> intended to use gcc, but I have discovered the problems.
>
> Has anybody resolved the porting issues for HP/UX and gcc? Or should
> I just bite the bullet and buy the HP compiler?
W
I've seen in the original SAX2 file I got that DocumentHandler has
been deprecated, while the one coming with Xerces, in CVS, right now
is not?
Is this a willing thing or just a forgotten thing?
Pier
--
- P
Hi,
I'll be doing Mac right after I get my build out to my client. Getting my
build
involved getting the library working right with Metrowerks Codewarrior for
Windows
and then making use of the xerces lib - I've already written most of the code
that
will go into my first delivery so it won'
Since it appears that no one is working on porting to either platform, I'm
going to start working on this. I'll be focusing on the OS/2 port for now --
probably for both VAC++ 4.0 and gcc 2.95/emx.
--Bill
Andy Clark wrote:
>
> Stefano Mazzocchi wrote:
> > I'm voting -1 on making Stylebook a full blown project under
> > xml.apache.org + creating a mail list + creating docs for users +
> > having questions on it and so on.
>
> We're not talking about making StyleBook a project. We're
> just making i
I have just started trying to port an application to HP/UX. We had
intended to use gcc, but I have discovered the problems.
Has anybody resolved the porting issues for HP/UX and gcc? Or should
I just bite the bullet and buy the HP compiler?
Dudley Irish
Stefano Mazzocchi wrote:
> I'm voting -1 on making Stylebook a full blown project under
> xml.apache.org + creating a mail list + creating docs for users +
> having questions on it and so on.
We're not talking about making StyleBook a project. We're
just making it possible for users to build the
55 matches
Mail list logo
