> > > 5. multiple interceptor chains per InvocationFactory, e.g. each method > > gets a separate interceptor chain. (Idea from current mbean interceptor > > implementation) > > > > Do we really need per method interceptor chains? We did not need them to > implement EJBs. >
After working with them a little bit with mbeans for jca 1.5 deployment, I conclude Yes, we absolutely need per-method interceptor chains!! they make life so much simpler I can't believe it. I'm less convinced that relying on a fixed sequence of interceptor factories to generate every chain is the best design. I implemented a quick and dirty way of generating custom chains by simply looking in the mbean metadata for a list of interceptor classes. This strikes me as a lot more convenient for my purposes than having to construct some long interceptor factory list that can be used for any chain. I think generating the interceptor chains needs some more thought. Bill, my impression is that you are planning to use your AOP framework as-is for the ejb conversion. Is there anything I can do to influence you towards using per-method interceptors from the start? Or do you think two smaller rewrites is a better plan than one larger rewrite? thanks david jencks ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
