[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Datatype interface extension
Are you saying that the allowed arguments of the isValid() method on the Datatype interface depends on the return value of the isContextDependent() method on a separate interface? That doesn't seem right to me. The Datatype interface should be semantically self-contained. I think the isContextDependent() method must be on the Datatype interface. This isn't so bad, as it's potentially useful for other applications independently of the Datatype compatibility spec. The getIdType() can be on a separate CompatibilityDatatype interface. --On 11 September 2001 16:42 -0700 Kohsuke KAWAGUCHI <kohsuke.kawaguchi@eng.sun.com> wrote: > > I implemented the CompatibilityDatatype interface, which has two methods > (isContextDependent and getIdType). > > I changed the documentation of the isValid (and related) methods so that > passing null context is OK as long as the datatype is > context-independent. > > > Is there any problem if I check in this code? > > regards, > -- > Kohsuke KAWAGUCHI +1 650 786 0721 > Sun Microsystems kohsuke.kawaguchi@sun.com > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC