[
https://issues.apache.org/jira/browse/OWB-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689554#action_12689554
]
Mark Struberg commented on OWB-87:
----------------------------------
Gurkan, is there a way we could actually set the current conversationId from
outside, instead of doing this in the ConversationComponent?
> protected Conversation createInstance(CreationalContext<Conversation>
> creationalContext)
> {
> String conversationId = JSFUtil.getConversationId();
Also the sessionId retrieval does not need to be JSF specific, isn't?
wdyt, any ideas?
> move all non-JSF specific parts of Conversations handling to an own general
> package
> -----------------------------------------------------------------------------------
>
> Key: OWB-87
> URL: https://issues.apache.org/jira/browse/OWB-87
> Project: OpenWebBeans
> Issue Type: Task
> Components: Context and Scopes
> Affects Versions: M1
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: M2
>
>
> Most of the conversation handling code is currently in the package
> > org.apache.webbeans.jsf
> but all non-JSF specific stuff should finally land in something like
> > org.apache.webbeans.conversation
> to also support common conversation functionality for e.g. a Wicket
> integration
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
