On Tue, May 25, 2010 at 7:57 AM, Dennis Reedy <[email protected]> wrote: > These are all good issues. I think more rigor needs to be put into how > service artifacts are updated, and what attributes we look for when we seek > to discover services. Using version numbers in both the produced artifacts > and ensuring that services advertise version numbers (as part of > net.jini.lookup.entry.ServiceInfo), and that we look for specific version > numbers for a service we want to use can help with this issue. > > Perhaps (and I'm not sure this has been discussed before) having a range of > versions that a service provides support for could also help address this > issue. If the client determines it is out of synch, the deferred update > approach certainly allows the client to choose to use remote class loading or > provision that requisite jars.
Normally I'm not a fan of using version ranges in Maven, but with long running services I think it probably makes sense. -jeff
