Re: DiscoveryAdmin, Reggie and Unicast discovery port.

Ok, that makes sense I'll make it a property, that should fix the test failures, the BindException will remain uncaught by default. - Original message - > > Only thing is, people do occasionally use unicast discovery.  For > instance, the Amazon cloud doesn’t support multicast (that may

Re: [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging

- Original message - > Hi Peter, > > I'm not sure we're on the same wavelength here, I've inlined some > comments below. > > Regards > > Dennis > > On Feb 21, 2014, at 553PM, Peter wrote: > > > To minimise the chances of duplicate class loading of service api and > > avoid implementat

Re: DiscoveryAdmin, Reggie and Unicast discovery port.

Only thing is, people do occasionally use unicast discovery. For instance, the Amazon cloud doesn’t support multicast (that may have changed since I looked into it). So in those cases, if you can’t come up on the chosen port, it is actually a failure. So I’d make the automatic failover featu

Re: [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging

Hi Peter, I'm not sure we're on the same wavelength here, I've inlined some comments below. Regards Dennis On Feb 21, 2014, at 553PM, Peter wrote: > To minimise the chances of duplicate class loading of service api and avoid > implementation class collisions. You'll never get duplicate cla

DiscoveryAdmin, Reggie and Unicast discovery port.

I'm currently getting a number of test failures where a port passed in by configuration is already in use. If the port specified is 0, then an arbitrary port is selected if 4160 is not available. However Reggie throws an exception during construction if a configured port is in use. I'd like

Build failed in Jenkins: river-qa-refactor-win5 #1

See -- [...truncated 16263 lines...] [java] Test Passed: OK [java] [java] - [java] com/sun/jini/test/spec/javaspace/conformance/snapshot/S

Re: [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging

To minimise the chances of duplicate class loading of service api and avoid implementation class collisions. This maximises compatibility among proxy's and services common service api classes. Granted, there will be cases where clients don't have service api loaded for particular services, in

Build failed in Jenkins: river-qa-refactoring #148

See Changes: [peter_firmstone] Ensure tasks calling addNotification with identical ServiceID's are not executed concurrently. -- [...truncated 15897 lines...] [java] ---

Re: [jira] [Commented] (RIVER-435) Proposed Standard for Single-Archive Service Deployment Packaging

To add to what Gregg has mentioned: Exported objects, that are Remote, but not services themselves, can be passed as parameters to services. If a service receives a remote object as a parameter and allows this object's smart proxy classes to load, then it's important for the proxy to only see t