[weld-issues] [JBoss JIRA] (WELD-1159) Deadlock between Weld AbstractContext session/application contexts creationLock

[Marek Schmidt (JIRA)]

Marek Schmidt commented on WELD-1159 Deadlock between Weld AbstractContext session/application contexts creationLock I can think of one possibility of a deadlock with the patch, although it is very synthetic and I am not sure if this pattern could be turned into something sane: @ApplicationScoped public class KnitProducer { @Inject Instance<PurlKnit> purlKnit; @Inject KnittingOrder knittingOrder; @Produces @ApplicationScoped public KnitPurl getKnitPurl() { if (knittingOrder.isKnitFirst()) { Purl purl = purlKnit.get(); purl.toString(); return new KnitPurl(purl); } else { return new KnitPurl(new Purl()); } } } @ApplicationScoped public class PurlProducer { @Inject Instance<KnitPurl> knitPurl; @Inject KnittingOrder knittingOrder; @Produces @ApplicationScoped public PurlKnit getPurlKnit() { if (!knittingOrder.isKnitFirst()) { KnitPurl knit = knitPurl.get(); knit.toString(); return new PurlKnit(knit); } else { return new PurlKnit(new Knit()); } } } @RequestScoped public class KnittingOrder { private boolean knitFirst; public boolean isKnitFirst() { return knitFirst; } public void setKnitFirst(boolean knitFirst) { this.knitFirst = knitFirst; } } @Typed({}) public class Purl ... @Typed({}) public class PurlKnit extends Purl ... @Typed({}) public class Knit ... @Typed({}) public class KnitPurl extends Knit ... (anyway, this case is infinitely less important than the original issue, so it should not block the patch)

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues