[ https://issues.apache.org/jira/browse/OWB-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089072#comment-16089072 ]
Romain Manni-Bucau commented on OWB-1202: ----------------------------------------- Hmm, this is interesting cause I read the spec the opposite way. Kind of "you manage the container then manage the container" API style. Assume we start ourself a thread then we need 1. define an OWB SPI to do it in the way the user wants (I see at least 3 different potential expectations: sync, async and managed, async and unamanaged) 2. ensure this API can start a thread (which is not required by spec AFAIK) 3. handle somehow (probably 1 but what about the default then) the case where you use it in a single threaded program :s [~johndament] anything you see in the spec making that request needed or wanted? > Don't require user to spin up a thread for long running SeContainer > ------------------------------------------------------------------- > > Key: OWB-1202 > URL: https://issues.apache.org/jira/browse/OWB-1202 > Project: OpenWebBeans > Issue Type: Improvement > Reporter: John D. Ament > > Suppose I have a main method that just does this > {code} > SeContainerInitializer.newInstance().initialize(); > {code} > I shouldn't be required to create a thread that will keep the container > alive. It would be better if OWB kept it alive for me. -- This message was sent by Atlassian JIRA (v6.4.14#64029)