Given a list of ModuleDefinition instances, it is obvious how a
Repository implementation can do a *linear* search using Query:
private List definitions;
public List findModuleDefinitions(Query constraint) {
List result = new ArrayList();
for(ModuleDefinition def : definitions
yet, to a large centralized repository, etc.).
// Bryan
Stanley M. Ho wrote:
Bryan Atsatt wrote:
And we haven't done so in the spec, either. I think we should.
Query was not declared as Serializable in the spec because it was
unclear if we wanted to allow custom Query implementations and
Bryan Atsatt wrote:
And we haven't done so in the spec, either. I think we should.
Query was not declared as Serializable in the spec because it was
unclear if we wanted to allow custom Query implementations and how it
might impact these custom Query implementations.
Now that we have de
If Query is made Serializable, let's make sure it declares a serial
version UID to enable serial compatibility of future versions.
Glyn
Bryan Atsatt <[EMAIL PROTECTED]> wrote on 23/05/2007 19:14:41:
> When I designed the Query/Repository model in the prototype, I had it
> firml
When I designed the Query/Repository model in the prototype, I had it
firmly in my mind that Query should be Serializable, so that it could be
sent over the wire to a remote repository. I've described it this way to
a number of people. But apparently I forgot to actually declare it. :^)
A
