Re: [webbeans-dev] Re: Distributed event channels
It is and remains my very strong view that unless we provide a very
easy-to-use mechanism that allows state synchronization between
stateful components to occur as part of the transaction completion
lifecycle, then actual web beans applications are going to be riddled
with bugs. They are going to break the minute a transaction rollback
occurs. Many Java EE applications already have this kind of bug, since
it is difficult to code for, and even more difficult to test for.
Since Web Beans encourages stateful components, these bugs will become
even more common!
I strongly agree, you really can't discard the event part of the spec
without understanding the consequences of doing so. Being able to hold
off events from being fired (and thus observers from being notified)
until the transaction completes successfully is a cornerstone of the
stateful programming model. I'd love to see what Gavin writes up
because perhaps I think it will make the feasibility much more clear.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat, Inc. | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction