Gurkan, I think I need help :)
Currently we set the Converation via the ConversationComponent which gets the conversationId from the FacesContext. The FacesContext is essentially the same thing as we already have with our WebBeansContext. It's 'simply' a ThreadLocal container for session/app/request/page information. So my idea was to store the conversationId in a kind of @RequestScoped bean at start of the ServletRequest, so the ConversationComponent doesn't need to get the cid from the FacesContext but instead simply asks this 'ConversationBean'. Hmm the longer I think about it, why don't we simply create the Conversation at request startup? My basic idea was: we should move the conversationId detection out of the ConversationComponent, and make it part of the 'integration stuff'. So for ServletContainers this may work different than for PortletBridges and also different for freaky things like a standalone Swing application. txs and LieGrue, strub
