[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865138#action_12865138
]
Joe Bergmark commented on OWB-369:
--
Gurkan, I believe this comes down to another case of tier
[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865142#action_12865142
]
Mark Struberg commented on OWB-369:
---
Imo ConversationManager should also get refactored to b
[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865159#action_12865159
]
Gurkan Erdogdu commented on OWB-369:
Joe,
As I said OWB not written for tiered-class load
I'm not sure I understand the point you are trying to make here Gurkan. Are
you saying you do not want to make changes that will allow OpenWebBeans to
work in tiered classloading environments? This isn't the first time an
issue like that has come up, and we have made several changes already.
As
Perhaps it would be more clear if detailed what I think is happening in this
particular example:
1) WebBeansFinder loads a single WebContextService per application (happens
during the Lifecycle init).
2) WebContextService calls "ConversationManager.getInstance();", which would
use the WebBeansFind
[
https://issues.apache.org/jira/browse/OWB-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865307#action_12865307
]
Gurkan Erdogdu commented on OWB-369:
I have changed WebBeansFinder Map> to
Map>. Also rem
[
https://issues.apache.org/jira/browse/OWB-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu closed OWB-357.
--
Assignee: Gurkan Erdogdu (was: Eric Covener)
Resolution: Fixed
Done.
> WebbeansFinder should index