On Wed, 28 Aug 2002 23:16, Nicola Ken Barozzi wrote: > > No they are versioned java interfaces in most cases. > > Hmmm... there is no imposition about this in Serviceable... hmmm...
But every container sans Merlin enforces this. > Ah, ok, I like this. > The doclet stuff, huh? > I thought it was already there :-) It is - but it uses a custome mechanism. Unification may be possible but it could also be a dose of everything looking like a nail ;) > But for this, I have the sense that it's overkill to get to this level, > to go down to /generic/ *method* attributes. > > So I can have Component lifestyle, method lifestyle... it gets me dizzy... lifestyle is an aggregation and interpretation of attributes and should not appear as one IMHO. > Now we are getting to a point in which the metadata describes the role, > right? essentially. > 1) use services via generic utility methods and loose strict type checking not really viable IMHO for programmer types like us ;) > 2) make the interface by hand, or the metadata by hand, or both, and > have a doclet-like system that keeps *both* in sync. Right - either quite insane or quite brilliant. -- Cheers, Peter Donald *------------------------------------------------* | The student who is never required to do what | | he cannot do never does what he can do. | | - John Stuart Mill | *------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
