[weld-issues] [JBoss JIRA] (WELD-2416) Memory behaviour of of javax.enterprise.inject.Instance.iterator().next vs. of javax.enterprise.inject.Instance.get() in Weld 1.1.18 vs. Weld 2.3.5

[Matej Novotny (JIRA)]

Title: Message Title

Matej Novotny commented on WELD-2416   Re: Memory behaviour of of javax.enterprise.inject.Instance<?>.iterator().next vs. of javax.enterprise.inject.Instance<?>.get() in Weld 1.1.18 vs. Weld 2.3.5 Digging a bit into this, I think that having Instance.get() and Instance.iterator() behave the same way is a good thing (e.g. the changes made as part of WELD-1320 make sense) Checking on the JMC, I can see that this problem is reproduceable on both version of Weld as long as CDIBean injects Instance<CDIBean2>. That might be the main trouble here - two dependent beans, one of which injects the other via Instance. Though I do not yet grasp what's the cause. The change in behaviour of Instance.iterator() is that previously all instances were created and handed over while now they get created on-demand when you invoke next(). Add Comment   This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)

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