> It makes some interceptors less complex to implement. It > makes sense at service interception where we may have a > separation between attributes/operations. Say I want to > persist 2 out of 3 attributes I'm changing. Operations don't > need the persistence interceptor, nor do all the attributes.
clearly the cache/persistence implementation are a justification of the method scoped interception Like bill showed at BootCamp I think the levels are method/instance/application (logical)/class/VM/cluster. today we have application only in EJB level where the logical scope is the EJB container and the JNDI/JMX name that identifies it. Dain does kindof interception on the abstract getter/setter so the method one is there. marcf ------------------------------------------------------- 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
