Seam always exposes the current conversation ID under the #{conversation.id} value-binding expression.
Seam 总是在 #{conversation.id}值绑定表达式下公开当前的对话。
Seam can differentiate between them if you specify the conversation ID before retrieving the component instance stub.
如果在检索组件实例存根之前指定了对话id,那么Seam就可以对它们进行区分。
To ensure that the conversation that holds this collection is reactivated during the remote call, the conversation ID must be established on the remoting context, as discussed earlier.
要想确保持有这个集合的对话能够在远端调用的过程中被重新激活,此对话id必须建立在remoting内容的基础上,正如本文之前讨论的那样。
应用推荐