-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Brock Sent: Thursday, February 05, 2004 1:52 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Bad cross module dependency
> > The naming stuff should be in common. > > You mean org.jboss.naming in server? Yes. > > The interceptor/invoker/proxy stuff needs to be unified across the > > jmx, aop, and server modules. Let's get this discussion going as this > > needs to be resolved now. > > I think the best model is provided by Bill's aop interceptors. > > The fundamental idea is that the interceptor makes no assumptions about what it is intercepting. > It simply asks the metadata object. The metadata object can be configured according to whatever joinpoints > are relevent. > i.e. field/method/constructor, jmx attribute/operation or it could even be a url if it were applied to servlets. > The deployer, container or invocation sets up the relevent metadata model. It is actually a hierarchy of > metadata providers, e.g. invocation, container, vm, cluster > > You'll notice one outstanding issue is the REVISIT on how to get a human readable string that represents > the joinpoint for error messages. > ... I'm going over this stuff now so I can propose what needs to change. The revist on the messages are due to the invocation not having a notion of a method. There is no notion of what the invocation is invoking, or just no valid toString form? ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
