Isn't List<URL> already present in the MarshalledInstance? Why repeat this as an Entry? Wouldn't it be easier to just add a public accessor to deserialize the list of URLs from MarshalledInstance.locBytes?
I apologize if this was already explained, but there's been a LOT of email to read on this list lately. Chris -----Original Message----- From: Dennis Reedy [mailto:dennis.re...@gmail.com] Sent: Saturday, May 22, 2010 9:29 AM To: river-dev@incubator.apache.org Subject: Re: Maven repository Entry was Re: Codebase service? [CJD] ... <snip> ... I would just go with a List<String> dlJars; With this you could provide support for retrieving the DL jar(s) for non-maven systems as well. If the dlJars property contains 1 element and is of the form groupId:artifactId:version:classifier, then maven resolution gets used. Otherwise the DL jars can be obtained using the codebase of the advertising service. For maven resolution, I think you'll also want to either provide support for parsing your maven settings.xml or include the repositories to go find the artifact if it's not present. If the artifact is retrieved from the repository it will have a message digest along side of it (with either a .sha1 or .md5 extension). That can be used to compare a locally computed digest HttpmdUtil.computeDigest() for updates. But that comparison really only needs to take place for snapshots, since by definition releases are considered immutable. IMO supporting transitive deps is a must have, without that we really dont get that far. A DL artifact may depend on another DL artifact, and that DL artifact may have deps as well.
