I'm not sure what you mean. Are you thinking something like this?: Entry[] entries=EntryAnnotationReader.readEntries(MyService.class);
So the EntryAnnotationReader is a utility class that knows how to introspect the class and translate its annotations to a set of Entry classes. Cheers, Greg. On Tue, 2012-10-02 at 08:32, Simon IJskes - QCG wrote: > On 25-09-12 11:26, Greg Trasuk wrote: > > > > On Tue, 2012-09-25 at 04:32, Simon IJskes - QCG wrote: > >> On 25-09-12 09:59, Dan Creswell wrote: > >>>> Glad you introduced ops teams. Would a middle ground be possible? Two > >>>> options: A annotation refering to a part in a deployment configuration > >>>> file, or using the annotations as defaults, and provide ops team with a > >>>> overriding option? > >>> I was edging towards the latter whilst scribbling the above... > >> > >> We need an id to hang overrides onto, so i've created the ServiceClass > >> annotation. Greg, are you ok with this? > >> > >> > > > > Sure. I suspect we need to flesh out some samples and see how they > > look, then edit the "annotation vocabulary". > > So we would create an 'EntryLookup' interface, and implement this with a > 'EntryIntrospector'? This concept can be extended with a registry that > contains a map<Class,Entry[]> or something like that, so we can prime > the lookup, for classes not annotated. > > Gr. Simon > > -- > QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl > Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
