From: Christophe Roux <ch_roux@club-internet.fr>
To: rhug-rhats@sources.redhat.com
Subject: transmission of serialized objects over a POST http request with rhug - patch solution
Date: Sat, 07 Sep 2002 10:01:00 -0000 [thread overview]
Message-ID: <E17nix8-0008AX-00@smarthost2.mail.easynet.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
I have 2 servlets communicating via a POST http request and trnasmitting a
serialized object.
It used to work fine with jdk and tomcat3.2.3.
I am on the road to gcj and rhug.
I found problems with the serialisation so that I build a small example with
two servlets which exchange a simple serialized object. This object contains
a Vector.
I had to change the code in gnu.gcj.protocol.http.Connection in order to have
a correct POST http request.
I send a gnats bug report with my solution to gcc but after one week, the bug
is still unasigned.
So I decided to give my correction to rhug users, allowing to patch gcj.
The Connection class is given in the tar joined to this mail.
After that, I found in rhug how to deserialise an object with the rhug class
loader, so that the MielMail object can be found by the receiving servlet
(M1.java). So I wrote a small class (MielObjectInputStream.java) for
deserialization class loading.
After that, there was a problem with deserialization of null objects in the
Vector of MielMail. I had to correct java.lang.ObjectInputStream.java because
there was a NullPointerException in a dump instruction.
In the joined tar file, I give all source files for these correction plus
exmaples classes.
I hope it can be usefull to rhug users and I also hope rhug gourous can point
out gcc developpers in order these bugs will be soon corrected in the gcc
release.
Yours sincerely,
Christophe Roux
[-- Attachment #2: postobje.tgz --]
[-- Type: application/x-gzip, Size: 13817 bytes --]
next reply other threads:[~2002-09-07 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 10:01 Christophe Roux [this message]
2002-09-07 12:14 ` Anthony Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17nix8-0008AX-00@smarthost2.mail.easynet.fr \
--to=ch_roux@club-internet.fr \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).