[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Ste Gr commented on WELD-2557 Re: Not all events are fired Thanks for your reply. The app and jar contains a lot of company internal code which I'm not allowed to share I could try to create a minimal example but I don't know if it will trigger the same behavior. Please let me know if I should do that. After some more debugging (with custom log messages) it must be some race condition. The whole CDI bootstrap happens in threads named "Weld Thread Pool – x" & "MSC service thread x-x". The step "START bootstrap > endInitialization" is then in a thread named "ServerService Thread Pool – xxx" which also fires the initialized event. It seems to work every time when enough log output is produced (which again makes it harder to debug) As as site note: It never failed with WildFly 10.0.1.Final Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2556) Draft new SPI for defining classes that will delegate to integrator implementations
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #83 in GitHub Weld / WELD-2556 Draft new SPI for defining classes that will delegate to integrator implementations Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matej Novotny commented on WELD-2557 Re: Not all events are fired Hello Ste Gr thanks for reporting the issue. Would you be able to share the example app you were using? I know it's not a reproducer but it may still be a good starting point. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matej Novotny updated an issue Weld / WELD-2557 Not all events are fired Change By: Matej Novotny Component/s: Servlet Container Support Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2556) Draft new SPI for defining classes that will delegate to integrator implementations
Title: Message Title Matej Novotny updated an issue Weld / WELD-2556 Draft new SPI for defining classes that will delegate to integrator implementations Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/83, https://github.com/weld/core/pull/1888 Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Ste Gr created an issue Weld / WELD-2557 Not all events are fired Issue Type: Bug Affects Versions: 3.0.5.Final Assignee: Unassigned Components: Servlet Container Support Created: 15/Jan/19 5:10 AM Environment: WildFly 15.0.1.Final, JDK 8 / JDK 11 Priority: Major Reporter: Ste Gr I have a war application that contains a jar with commonly used code. Both contain a beans.xml set to version 2.0 and both have a application-scoped bean with an observer method for the initialized event of the application scope. Additionally both have an observer method for the destroyed event of the application scope. My observation is that only the observer inside the war is fire 100% of the time. The initialized-observer in the jar is sometimes ignored. I can't find any pattern when it fires and when not. The destroyed-observer is always fired in both cases (even if the initialized-observer didn't fire). I'm not able to debug the whole thing because it always works as soon as I start the server in debug mode.
[weld-issues] [JBoss JIRA] (WELD-2422) Revisit Weld SPI so that integrators are not required to depend on Weld internals
Title: Message Title Matej Novotny commented on WELD-2422 Re: Revisit Weld SPI so that integrators are not required to depend on Weld internals Moving this issue away from 3.1.0.Final release as the implementation is too time consuming to meet the deadline. Once implemented, this issue should be part of a Weld release which bumps minor version due to the API/SPI changes it will bring. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2422) Revisit Weld SPI so that integrators are not required to depend on Weld internals
Title: Message Title Matej Novotny updated an issue Weld / WELD-2422 Revisit Weld SPI so that integrators are not required to depend on Weld internals Change By: Matej Novotny Fix Version/s: 3.1.x Fix Version/s: 3.1.0.Final Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
