2009/5/30 Michael Youngstrom <youngm(a)gmail.com>:
I'm not really happy with this solution. Over the last couple
hours I've really grown to like the power of a more servlet general
conversation available to the full request. If a developer doesn't
care about using a request parameter they shouldn't have to live with
the post Filter restriction.
I'm also finding this idea to be pretty seductive.
Isn't there some way we can make the conversation context more
pluggable/extensible itself? WebBeans could ship with a general
friendly request parameter based conversation propagation mechanism
and other frameworks like Wicket could replace or extend the provided
Conversation Manager to better fit their propagation requirements
along with the potential limitations?
In this release I don't want to do something extremely complex here.
If there is a simple solution that covers the major integration
usecases that we can think of, fine, let's go with it. But if not, I
would rather defer it.