[weld-issues] [JBoss JIRA] (WELD-2563) In a CDI SE application, three instances of every Service loaded are created; only one is used
Title: Message Title Laird Nelson commented on WELD-2563 Re: In a CDI SE application, three instances of every Service loaded are created; only one is used One other comment. I note that in the javadocs there is this sentence: "The ResourceLoader is a per-BeanManager service." But that does not appear to be the case in my situation. I'm not sure if that documentation needs to be corrected or not. 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-2563) In a CDI SE application, three instances of every Service loaded are created; only one is used
Title: Message Title
Laird Nelson commented on WELD-2563
Re: In a CDI SE application, three instances of every Service loaded are created; only one is used
I note that in a CDI SE environment, the three {{ResourceLoader}}s will be, by default: 1. WeldResourceLoader (created by the SeContainerInitializer implementation and not overridable) 2. WeldClasspathResourceLoader (created by AdditionalServiceLoader#getResourceLoaders()) 3. DefaultResourceLoader (created by AdditionalServiceLoader#getResourceLoaders()) Could we detect this situation and simply use the WeldResourceLoader in that case?
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-2563) In a CDI SE application, three instances of every Service loaded are created; only one is used
Title: Message Title
Laird Nelson edited a comment on WELD-2563
Re: In a CDI SE application, three instances of every Service loaded are created; only one is used
I note that in a CDI SE environment, the three {{ ResourceLoader ResourceLoaders }} s will be, by default:1. {{WeldResourceLoader}} (created by the {{SeContainerInitializer}} implementation and not overridable)2. {{WeldClasspathResourceLoader}} (created by {{AdditionalServiceLoader#getResourceLoaders()}})3. {{DefaultResourceLoader}} (created by {{AdditionalServiceLoader#getResourceLoaders()}})Could we detect this situation and simply use the {{WeldResourceLoader}} in that case?
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-2563) In a CDI SE application, three instances of every Service loaded are created; only one is used
Title: Message Title Laird Nelson created an issue Weld / WELD-2563 In a CDI SE application, three instances of every Service loaded are created; only one is used Issue Type: Bug Affects Versions: 3.0.5.Final Assignee: Unassigned Components: Bootstrap and Metamodel API Created: 06/Feb/19 2:16 PM Priority: Major Reporter: Laird Nelson (See this forum message for details.) I have a CDI SE application (flat classpath). I have a JpaInjectionServices implementation with a corresponding META-INF/services entry. I notice that it is instantiated three times by Weld, but only the first instance is used. I believe this is because the code in AdditionalServiceLoader loads the service using three distinct ResourceLoaders: the single ClasspathResourceLoader used by the Deployment, the WeldClasspathResourceLoader used always when loading additional services, and the DefaultResourceLoader used always when loading additional services. At the very least it seems that there should be some documentation that indicates that a Service will be instantiated in a CDI SE application a minimum of three times, and only the first of those three instances will be used.
[weld-issues] [JBoss JIRA] (WELD-2562) Revisit documentation generation process with newer tools
Title: Message Title Matej Novotny created an issue Weld / WELD-2562 Revisit documentation generation process with newer tools Issue Type: Task Affects Versions: 3.1.0.Final Assignee: Unassigned Components: Documentation Created: 06/Feb/19 5:51 AM Priority: Major Reporter: Matej Novotny While generating docs for the release, we leverage Gradle. Newer version of Gradle apparently require JDK 9+ but if provided, then our ancient asciidoctor-maven-plugin fails. Upgrading this plugin in turn yields errors in doc formatting. We should, in general, investigate generating docs on newer Javas and upgrade plugin and docs themselves accordingly. Note that you can generate docs regardless of Gradle of course and so it should be reproducible just by using JDK 9+.! Add Comment
[weld-issues] [JBoss JIRA] (WELD-2562) Revisit documentation generation process with newer tools
Title: Message Title Matej Novotny updated an issue Weld / WELD-2562 Revisit documentation generation process with newer tools Change By: Matej Novotny Fix Version/s: 3.1.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-2550) InterceptionFactory with loosened limitation on interfaces
Title: Message Title Xavier Dury commented on WELD-2550 Re: InterceptionFactory with loosened limitation on interfaces Matej Novotny I've tested your change and found it good enough for the use-cases I had in mind. It also proves that the concept is viable and that it could be further debated/refined by the EG. Thanks! 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-2553) Update specs versions to match EE8
Title: Message Title Matej Novotny updated WELD-2553 Weld / WELD-2553 Update specs versions to match EE8 Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done 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
