public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nicolas Geoffray <nicolas.geoffray@menlina.com>
To: mauve-discuss@sources.redhat.com
Subject: Re: tests with rmic
Date: Wed, 19 Oct 2005 08:10:00 -0000	[thread overview]
Message-ID: <4355FF5C.10204@menlina.com> (raw)

Hi Audrius

Meskauskas Audrius wrote:

>
> I looked at our gnu.java.rmi.server.UnicastRef and - yes, 
> unfortunately it seems that there is system property in Classpath that 
> would force the object serialization even if the RMI client and server 
> are in the same machine.
>
> If you plan serious testing work, we should probably add such property 
> as a necessary testing tool, but altering RMI implementation requires 
> to have a test suite first. I think, you can commit such tests anyway 
> because the object serialization is not the only thing in RMI that 
> deserves testing.
>
Unfortunately I do not plan for the moment serious rmi testing work. I 
just wanted to report a bug within gnu classpath. Because the test 
involves launching at least 2 vms, it's difficult to reveal the bug. The 
property forcing serialization would be great in my case!

Cheers,
Nicolas

             reply	other threads:[~2005-10-19  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  8:10 Nicolas Geoffray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-17 17:13 Nicolas Geoffray
2005-10-18  2:37 ` Chris Abbey
2005-10-18  8:41 ` tests with rmic! Meskauskas Audrius
2005-10-18 11:47   ` Nicolas Geoffray
2005-10-18 18:10     ` tests with rmic Meskauskas Audrius

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=4355FF5C.10204@menlina.com \
    --to=nicolas.geoffray@menlina.com \
    --cc=mauve-discuss@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).