Thanks Bill,
Sounds interesting, let us know how you get on, maybe you could send us
some screen shots and we could feature it on our website?
There's an updated version of Browser available at the following link,
it uses the River 3.0 Startable interface, which was introduced to
support
Dear Peter,
Thanks for offering a patch, but that won't be necessary, as I can work around
the shutdown problem by just dumping the JVM through System#exit(..), and the
sluggishness problem by just being patient.
I checked the shutdown bug on 3.0.1 and it still persists in a modified
form,
Thanks Bill,
I suspect the thread bug was fixed in 3.0.1, are you able to confirm?
I think I can provide a fix for sluggish discovery.
One of the changes with River 3.0 was to remove instances of unsafe
publication, that is allowing a reference to "this" to escape during
object construction.
Hi Peter,
More from theseasonal djinn…
So, I had a littlemore patience with River 3.0’s unadorned
LookupDiscoveryManager,and it did indeed recognised the existence of an already
running 3.0djinn, but only after a fashion. River 2.3.3’sLookupDiscoveryManager
recognises the same djinn
Hi Bill,
Are you trying to discover a lookup service provided by River 2.2.X?
Which version of discovery are you using? V2 is now enabled by default
in 3.0.X, you won't discover any V1 lookup services unless you enable it
by passing in a ConstrainableLookupLocator using InvocationConstraint
