[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu created an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Issue Type: Bug Affects Versions: 3.1.0.Final Assignee: Unassigned Attachments: stackTrace.txt Components: Infrastructure, Servlet Container Support Created: 28/Feb/19 12:37 PM Priority: Major Reporter: Carlos Aristu I've an standard web project built in Eclipse. My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xml When I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes (Attached you can find the complete stack trace) The problem is caused because the WebAppBeanArchiveScanner is finding my beans.xml file twice: 1) When invoking the scan method of the parent DefaultBeanArchiveScanner class when looking for the META-INF/beans.xml 2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See here. This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9. Note that with this the same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble.
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Carlos Aristu I've an standard web project built in Eclipse. My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xmlWhen I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: *_WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes_* (Attached you can find the complete stack trace)The problem is caused because the [WebAppBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java] is finding my beans.xml file twice:1) When invoking the scan method of the parent [DefaultBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/common/src/main/java/org/jboss/weld/environment/deployment/discovery/DefaultBeanArchiveScanner.java#L75] class when looking for the META-INF/beans.xml2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L103].This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9.Note that 1: with this the same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble. Note 2: this problem usually does not happen when deploying the context in Tomcat without using Eclipse. In this case the beans.xml file is placed at WEB-INF/classes/META-INF/beans.xml. As this path contains the keyword "WEB-INF" the result found by the DefaultBeanArchiveScanner is discarded here. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Carlos Aristu I've an standard web project built in Eclipse. My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xmlWhen I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: *_WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes_* (Attached you can find the complete stack trace)The problem is caused because the [WebAppBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java] is finding my beans.xml file twice:1) When invoking the scan method of the parent [DefaultBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/common/src/main/java/org/jboss/weld/environment/deployment/discovery/DefaultBeanArchiveScanner.java#L75] class when looking for the META-INF/beans.xml2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L103].This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9.Note 1: with this the same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble.Note 2: this problem usually does not happen when deploying the context in Tomcat without using Eclipse. In this case the beans.xml file is placed at WEB-INF/classes/META-INF/beans.xml. As this path contains the keyword "WEB-INF" the result found by the DefaultBeanArchiveScanner is discarded [ here |https://github . com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L80]. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Carlos Aristu I've an standard web project built in Eclipse. My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xmlWhen I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: *_WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes_* (Attached you can find the complete stack trace)The problem is caused because the [WebAppBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java] is finding my beans.xml file twice:1) When invoking the scan method of the parent [DefaultBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/common/src/main/java/org/jboss/weld/environment/deployment/discovery/DefaultBeanArchiveScanner.java#L75] class when looking for the META-INF/beans.xml2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L103].This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9.Note 1: with this the same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble.Note 2: this problem usually does not happen when deploying the context applicaton in Tomcat without using Eclipse. In this case the beans.xml file is placed at WEB-INF/classes/META-INF/beans.xml. As this path contains the keyword "WEB-INF" the result found by the DefaultBeanArchiveScanner is discarded [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L80]. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Carlos Aristu I've an standard web project built in Eclipse. My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xmlWhen I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: *_WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes_* (Attached you can find the complete stack trace)The problem is caused because the [WebAppBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java] is finding my beans.xml file twice:1) When invoking the scan method of the parent [DefaultBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/common/src/main/java/org/jboss/weld/environment/deployment/discovery/DefaultBeanArchiveScanner.java#L75] class when looking for the META-INF/beans.xml2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L103].This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9.Note 1: with this the same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble.Note 2: this problem usually does not happen when deploying the applicaton in Tomcat without using Eclipse. In this case the beans.xml file is placed at WEB-INF/classes/META-INF/beans.xml. As this path contains the keyword "WEB-INF" the result found by the DefaultBeanArchiveScanner is discarded [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L80]. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Carlos Aristu I've an standard web project built in Eclipse IDE . My project makes uses of weld and my beans.xml is placed at the following location: build/classes/META-INF/beans.xmlWhen I try to start Tomcat, the following exception is thrown:java.lang.IllegalStateException: *_WELD-ENV-33: Invalid bean archive scanning result - found multiple results with the same reference: /home/openbravo/src/weld/pi-weld-upgrade/build/classes_* (Attached you can find the complete stack trace)The problem is caused because the [WebAppBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java] is finding my beans.xml file twice:1) When invoking the scan method of the parent [DefaultBeanArchiveScanner|https://github.com/weld/core/blob/master/environments/common/src/main/java/org/jboss/weld/environment/deployment/discovery/DefaultBeanArchiveScanner.java#L75] class when looking for the META-INF/beans.xml2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L103].This is causing that Tomcat can not be started using Eclipse. This problem can be reproduced using Tomcat 8, 8.5 and 9.Note 1: with this same project structure and location of the beans.xml file, and using and older version of weld (I've tried with 1.1.24) Tomcat 8, 8.5 and 9 start without trouble.Note 2: this problem usually does not happen when deploying the applicaton in Tomcat without using Eclipse. In this case the beans.xml file is placed at WEB-INF/classes/META-INF/beans.xml. As this path contains the keyword "WEB-INF" the result found by the DefaultBeanArchiveScanner is discarded [here|https://github.com/weld/core/blob/master/environments/servlet/core/src/main/java/org/jboss/weld/environment/servlet/deployment/WebAppBeanArchiveScanner.java#L80]. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Hello Matej, thank you for the response. Yes, when directly deploying my application into Tomcat I have no problem because I place the beans.xml file into WEB-INF folder as stated in the docs. This works fine. This problem happens in my "local" web application, when I start Tomcat using Eclipse IDE (for example when I need to debug my application). My application has the folder structure of a standard Eclipse dynamic web application. Having said that, I have found two different alternatives but both are failing depending on the Tomcat version I use: a) Deploy beans.xml into build/classes/META-INF/beans.xml --> With this approach I'm able to start my application with Tomcat 7. But using Tomcat 8 (or higher) results in the WELD-ENV-33 error. b) Deploy beans.xml into WebContent/WEB_INF/beans.xml --> With this approach I'm able to start my application with Tomcat 8 (or higher). But using Tomcat 7, the beans.xml file is not found. Note that option a) was working fine for me both in Tomcat 7 and 8 using weld 1.1.24 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-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Carlos Aristu commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse I am comparing between those versions because I'm currently working to upgrade weld in my web application, from version 1.1.24 to 3.1.0. I know that a lot of changes have been introduced between those versions, but I commented this just because having the same project configuration, this could look like a regression regarding Tomcat startup functionallity using Eclipse. Regarding how the deployment is made, I make use of the Eclipse server option "Serve modules without publishing"[1], this way I'm serving the application directly from my workspace. For the moment the best solution I have been able to achieve is to deploy the beans.xml in WebContent/WEB_INF/beans.xml inside my sources path. With this configuration: 1) I'm able to start Tomcat 8 (or higher) in Eclipse in all the cases 2) I'm able to start Tomcat 7 in Eclipse without making use of the "Serve modules without publishing" option 3) Tomcat 7 does not start in Eclipse if I make use of the "Serve modules without publishing" option [1] https://stackoverflow.com/a/16385765/8579169 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-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title
Carlos Aristu edited a comment on WELD-2570
Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse
I am comparing between those versions because I'm currently working to upgrade weld in my web application, from version 1.1.24 to 3.1.0. I know that a lot of changes have been introduced between those versions, but I commented reported this just because having the same project configuration, this could look like a regression regarding Tomcat startup functionallity using Eclipse.Regarding how the deployment is made, I make use of the Eclipse server option "Serve modules without publishing"[1], this way I'm serving the application directly from my workspace.For the moment the best solution I have been able to achieve is to deploy the beans.xml in WebContent/WEB_INF/beans.xml inside my sources path. With this configuration:{color:#00875A}1){color} I'm able to start Tomcat 8 (or higher) in Eclipse in all the cases{color:#00875A}2){color} I'm able to start Tomcat 7 in Eclipse without making use of the "Serve modules without publishing" option{color:#DE350B}3){color} Tomcat 7 does not start in Eclipse if I make use of the "Serve modules without publishing" option[1] https://stackoverflow.com/a/16385765/8579169
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-2575) Inject Interface with Generic Type is not working
Title: Message Title
Carlos Aristu updated an issue
Weld / WELD-2575
Inject Interface with Generic Type is not working
Change By:
Carlos Aristu
Let's suppose that I have the following interface:{code:java}public interface A {}{code}And the following injection point:{ { code:java} public class B { ... @Inject @Any private Instance> injectedInstances; ... } {code } } Then no instances of A are injected, I need to use wildcards to make it work: { { code:java} public class B { ... @Inject @Any private Instance> injectedInstances;} {code } } Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
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-2575) Inject Interface with Generic Type is not working
Title: Message Title
Carlos Aristu updated an issue
Weld / WELD-2575
Inject Interface with Generic Type is not working
Change By:
Carlos Aristu
Let's suppose that I have the following interface:{ { code:java} public interface A {} {code } } And the following injection point:{{public class B { ... @Inject @Any private Instance> injectedInstances;} }}Then no instances of A are injected, I need to use wildcards to make it work: {{public class B { ... @Inject @Any private Instance> injectedInstances;} }}Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
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-2575) Inject Interface with Generic Type is not working
Title: Message Title
Carlos Aristu created an issue
Weld / WELD-2575
Inject Interface with Generic Type is not working
Issue Type:
Bug
Affects Versions:
3.1.0.Final
Assignee:
Unassigned
Created:
04/Apr/19 7:09 AM
Priority:
Major
Reporter:
Carlos Aristu
Let's suppose that I have the following interface: {{public interface A { }}} And the following injection point: {{public class B { ... @Inject @Any private Instance> injectedInstances; } }} Then no instances of A are injected, I need to use wildcards to make it work: {{public class B { ... @Inject @Any private Instance> injectedInstances; } }} Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
Add Comment
[weld-issues] [JBoss JIRA] (WELD-2575) Inject Interface with Generic Type is not working
Title: Message Title
Carlos Aristu updated an issue
Weld / WELD-2575
Inject Interface with Generic Type is not working
Change By:
Carlos Aristu
Let's suppose that I have the following interface:{code:java}public interface A {}{code}And the following injection point:{code:java}public class B { ... @Inject @Any private Instance> injectedInstances; ...} {code}Then no instances of classes implementing A are injected, I need to use wildcards to make it work: {code:java}public class B { ... @Inject @Any private Instance> injectedInstances;}{code}Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
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-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title
Carlos Aristu updated an issue
Weld / WELD-2575
Inject of Interfaces with Generic Type is not working
Change By:
Carlos Aristu
Let's suppose that I have the following interface:{code:java}public interface A MyInterface {}{code}And the following injection point:{code:java}public class B MyClassWithInjectionPoint { ... @Inject @Any private Instance< A MyInterface > injectedInstances; ...} {code}Then no instances of classes implementing A are injected, I need to use wildcards to make it work: {code:java}public class B MyClassWithInjectionPoint { ... @Inject @Any private Instance< A MyInterface > injectedInstances;}{code}Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
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.jbos
[weld-issues] [JBoss JIRA] (WELD-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2575 Inject of Interfaces with Generic Type is not working Change By: Carlos Aristu Summary: Inject Interface of Interfaces with Generic Type is not working 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-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title
Carlos Aristu updated an issue
Weld / WELD-2575
Inject of Interfaces with Generic Type is not working
Change By:
Carlos Aristu
Let's suppose that I have the following interface:{code:java}public interface MyInterface {}{code}And the following injection point:{code:java}public class MyClassWithInjectionPoint< U T > { ... @Inject @Any private Instance U T >> injectedInstances; ...} {code}Then no instances of classes implementing A are injected, I need to use wildcards to make it work: {code:java}public class MyClassWithInjectionPoint< U T > { ... @Inject @Any private Instance> injectedInstances;}{code}Is this the expected behavior? Note: I have detected this problem after upgrading the Weld version I use from 1.1.24 to 3.1.0. In 1.1.24 this was working fine for me.
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
[weld-issues] [JBoss JIRA] (WELD-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title Carlos Aristu edited a comment on WELD-2575 Re: Inject of Interfaces with Generic Type is not working Hello, I've just updated the example to clarify, using the same type. I know that is a big leap between two versions, I was just mentioning it because for me it looked like a regression. What is the recommended approach under this scenario? Should I define the injection point using the wildcard(?) or is there any other better alternative? Thank you in advance. 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-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title Carlos Aristu commented on WELD-2575 Re: Inject of Interfaces with Generic Type is not working Hello, I've just updated the example to clarify, using the same type. I know that is a big leap between two versions, I was just mentioning it because for me it looked like a regression. What is the recommended approach under this scenario? Should I define the injection point using the wildcard or is there any other better alternative? Thank you in advance. 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-2575) Inject of Interfaces with Generic Type is not working
Title: Message Title Carlos Aristu commented on WELD-2575 Re: Inject of Interfaces with Generic Type is not working Thanks, in my use case it did not make sense to define that class as abstract. So I've fixed the problem by using wildcards. Thanks for the quick response. You can close this issue if you want. 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-2581) Illegal reflective access warning appears using JDK12+
Title: Message Title Carlos Aristu updated an issue Weld / WELD-2581 Illegal reflective access warning appears using JDK12+ Change By: Carlos Aristu An illegal-access warning may appear when starting the servlet container (i.e. Tomcat) using JDK12+ :...INFO: WELD-ENV-20: Using jandex for bean discoveryWARNING: An illegal reflective access operation has occurredWARNING: Illegal reflective access by org.jboss.weld.util.bytecode.ClassFileUtils$1 (file: .. / home/openbravo/src/openbravo/Openbravo/ WeldIllegalAccessWarn/WebContent/WEB-INF/lib/weld-core-impl-3.1.1.Final.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)WARNING: Please consider reporting this to the maintainers of org.jboss.weld.util.bytecode.ClassFileUtils$1WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operationsWARNING: All illegal access operations will be denied in a future release...Note that this warning does not appear if setting the JDK runtime with the parameter --add-opens=java.base/java.lang=ALL-UNNAMED Attached a war file with a simple web app to reproduce the problem + log file Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505)
