[cdi-dev] Thread safety of SeContainer and SeContainerInitializer

John Ament john.ament at spartasystems.com
Wed Dec 7 16:01:00 EST 2016

I would say that this is not guaranteed.

From: cdi-dev-bounces at lists.jboss.org <cdi-dev-bounces at lists.jboss.org> on behalf of Laird Nelson <ljnelson at gmail.com>
Sent: Wednesday, December 7, 2016 3:56 PM
To: cdi-dev at 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.

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20161207/2da909d8/attachment.html 

More information about the cdi-dev mailing list