On Wed, Apr 22, 2009 at 9:45 PM, Shane Bryzak <shane.bryzak@jboss.com> wrote:
Ok here's a special case - how about the Mutable interface/AbstractMutable?  These classes are used in the drools, framework, spring and persistence modules, and are referenced in the JavaBeanInterceptor and RootInterceptor.

These are classes we need to rethink, IMO. They are the foundation of the MEI, which we just cannot allow into Seam 3 until we set some clear goals in how it is going to work. It has been the source of a lot of pain developers have with Seam. I'm not saying it's all bad, but rather we can't just copy this stuff in without understanding its purpose and scope.

-Dan

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.