Step 1 would be just the jndi server mbean and remoting which is why this is as simply as it gets. Beyond that is how to integrate other services via the aop stuff. I want to see how the existing services are going to use these new frameworks.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, March 02, 2003 12:17 PM Subject: Re: [JBoss-dev] Proposal for jboss-wide interceptor framework > No No!! War War War!!! > > :-)) > > Actually I just wanted to get the discussion started early on and try to > get people involved since I think it will be a big undertaking to convert > all the interceptor models to a single one. I don't want to spring an > entire system conversion on anyone without a lot of warning. > > I don't see how your proposed example is simple since I think it involves > at least converting the remoting framework and probably the aop stuff. > > I was thinking of working in this order: > > mbeans > remoting > client interceptors > ejb interceptors > other. > > Aop could be converted at any time Bill agrees: I think this model is close > enough to his that this conversion should be fairly easy. I think the main > difference is the per-method interceptor stacks, which can probably be not > used at first. > > mbeans should also be fairly easy since I think this model is also close to > the mbean interceptor one. > > thanks > david ------------------------------------------------------- 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
