On 29-10-12 00:58, Gregg Wonderly wrote:
Clearly providing a proxy connection manger which becomes the hub
of the entire mechanism can create more problems then the single
problem that needs to be solved with NAT traversal or other network
routing.
I think you misunderstand the concept i'm
Hi Simon
Thats sounds great. Please upload the code in the river and also provide the
documentation. Your solution is pretty exciting.
RegardsBishnu
Bishnu Prasad Gautam
Date: Fri, 2 Nov 2012 08:15:23 +0100
From: si...@qcg.nl
To: dev@river.apache.org
Subject: Re: internet version
On
Ok, found the problem, there's a bug on line 99 in
net.jini.loader.RiverClassLoader
You didn't really test this properly did you?
No biggy.
Too busy to help any further (2 hour road trip now).
Peter.
Peter Firmstone wrote:
Ok I've had a brief look at debugging failing tests, it's worth
On 02-11-12 11:06, Peter Firmstone wrote:
Ok I've had a brief look at debugging failing tests, it's worth noting
that these tests now failing on my machine, passed two months ago with
flying colours.
I remember something different, and as your are implying it is due to
changes after your
On 02-11-12 11:15, Peter Firmstone wrote:
Ok, found the problem, there's a bug on line 99 in
net.jini.loader.RiverClassLoader
You didn't really test this properly did you?
No biggy.
Too busy to help any further (2 hour road trip now).
Peter.
Oh you are good! Thank you! Now we are getting
See https://builds.apache.org/job/River-QA-ubuntu-jdk7/56/changes
Changes:
[sijskes]
[sijskes] moved @beta to api.
[sijskes] moved @beta to api.
[sijskes] moved @beta to api.
--
[...truncated 8937 lines...]
[java]
