> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Sacha > Labourey > Sent: Monday, February 24, 2003 10:33 AM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] org.jboss.aop.MethodMetaData > > > > When an > > Interceptor wants metadata, it walks the chain. Each > > repository decides > > whether or not it can resolve the metadata, or how to resolve > > the metadata > > reference based on the context of the Invocation. For example, for > > MethodMetaData, the context of the Invocation is the method > > name. My main > > goal here it to: > > > > 1) Allow metadata to be programmitcally overriden generically > > at runtime > > > > 2) Allow default metadata to be defined within an > > application, JVM, and also > > cluster-wide. > > And I really love that. Though I don't think it is the role of the > interceptor to iterate over the Repositories but instead to some other > component (such as the repository itself) to delegate the > resolution down to > the chain. It makes me think to the exact opposite of the Clasloader > mechanism: try to load locally and if not present, ask parent > (i.e. Servlet > mode) > >
I disagree. The MetadataRepository should not have a concept of a parent. Think of it this way. You hava Class metadata that applies to multiple classes. One Class is configured to belong to one Cluster partition, a different class belongs to another. Is that a good enough use case? The invocation object receives the chain of references to the repositories as an Arraylist. The interceptor asks the invocation object to resolve the metadata for it. Bill ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
