> Could I propose that with regard to DB-backed persistent
> objects, Feature objects store the unique id of the feature
> within them and containsFeature only returns true if the
> feature of that unique ID is a child of another feature whose
> feature unique id places it somewhere on the dir
I've been trying to locate the biojava-acedb package, and all I've been
able to get is from the CVS server -- however, the CVS server shows that
these files are over a year old.
I'm using v1.21 of the Biojava package, and attempted to build this and got
the several compiler errors, and warnings
On Thu, Apr 04, 2002 at 11:52:53AM +0100, Matthew Pocock wrote:
> Hum,
>
> I would be happy if equals and hashCode on feature worked by being
> equivalent to delegating to the return value of makeTemplate - this includes
> all info except the children and parent. Since features can access both
>
On Fri, 5 Apr 2002, Schreiber, Mark wrote:
> I suppose two features from different sequences/ feature holders could
> produce the same template but like you say there is no easy way around
> this. We could specify that features only look to see if the have the
> same chain of parents, ignoring ch
I suppose two features from different sequences/ feature holders could
produce the same template but like you say there is no easy way around
this. We could specify that features only look to see if the have the
same chain of parents, ignoring children. However a Sequence if
converted to a GenBank
Hum,
I would be happy if equals and hashCode on feature worked by being
equivalent to delegating to the return value of makeTemplate - this includes
all info except the children and parent. Since features can access both
children and parents, you would potentialy get into a circular stack if you
