Re: [cdi-dev] Thread safety of SeContainer and SeContainerInitializer

I would say that this is not guaranteed. ________________________________ From: cdi-dev-bounces(a)lists.jboss.org <cdi-dev-bounces(a)lists.jboss.org&gt; on behalf of Laird Nelson <ljnelson(a)gmail.com&gt; Sent: Wednesday, December 7, 2016 3:56 PM To: cdi-dev(a)lists.jboss.org Subject: [cdi-dev] Thread safety of SeContainer and SeContainerInitializer Are SeContainer and SeContainerInitializer safe for concurrent use by multiple threads? The string "concurren" shows up only four times in the 2.0 specification but not in this context. I'm most interested in whether it is guaranteed that one thread may call SeContainer::initialize and another may call SeContainer::close. I'm assuming that this is not guaranteed. Best, Laird ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.