Its better to use the conversation-context, because then you can exactly control how long the state exists and you don´t have to remove it manually from the context. If you have a long message-list with a lot of data the session context is not appropriate. The session-context should be used only for data needed for the whole session, like user date for example.
Anyhow, you can access the session-context with:
thanks for the help. I know a long message list with a lot of data is not good for the session context. but the conversational context is not appropriate either. because for the list page, use can do a lot of things, like sorting, paging, and there is really no clear place to end the conversation.
i think that's also why the message list example provided in the Seam download uses session component.