[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Matěj Novotný updated WELD-2570 Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matěj Novotný Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse PRs are merged and these changes will land in next releases for Weld 3 and 4. Tassilo karge thank you for contribution and reproducer project! Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Hmm, if numberguess doesn't trigger, then I don't think there is any. You'd need to cobble something simple together. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Tassilo karge commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Is there a simple sample application that I can deploy on a tomcat, which actually uses the WebAppBeanArchiveScanner? I have looked at the numberguess example, but it does not use it. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matěj Novotný Git Pull Request: https://github.com/weld/core/pull/2003, https://github.com/weld/core/pull/2004 Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Issue was automatically transitioned when karge-itestra created pull request #2004 in GitHub Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: karge-itestra Status: Reopened Pull Request Sent Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Martin Kouba commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse 2) By the WebAppBeanArchiveScanner itself when looking for the /WEB-INF/classes/META-INF/beans.xml. See here. Carlos Aristu Tassilo karge So you're basically mapping /WEB-INF/classes to the build/classes directory? Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Thanks, I will look at it some time this week. Meanwhile, Tassilo karge, would you be able to provide steps to reproduce? E.g. some concise step by step summary on how to reproduce this issue so that we have a reference here (since we cannot create an automated test for this). Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Tassilo karge edited a comment on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Is there a plan to have a fix in a future version? I would like to weigh in on a fix of this issue.The WebAppBeanArchiveScanner does not do appropriate equality checks on the paths it discovers in two different ways. When a server.xml (admittedly NOT deployed via a WAR) specifies a resource directory like this (replace ... with a custom path):```xml```the DefaultBeanArchiveScanner returns `C:\...\target\classes\META-INF\beans.xml` as one of the beans paths. Afterwards, the WebAppBeanArchiveScanner does _substring matching_ to determine whether the path contains `WEB-INF\classes` (which the path does not). It then asks the servelet context for the beans.xml resource in the server´s `WEB-INF\classes\META-INF` directory, and resolves it to the _real_ file url which is again `C:\...\target\classes\META-INF\beans.xml`. Thus, the same resource is found twice.The problem is that substring matching is used to determine whether two semantically different URLs are the same. One of the URLs is the _logical_ path to the file from the server´s view and one is the _real_ path to the file. A simple fix to the issue would be to perform the path comparison _after_ the real file path of the beans.xml was resolved.However, I am not sure whether it would match with the specification to , since I do not know the relevant part. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ weld-issues mailing list weld-issues@lists.jboss.org
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Matěj Novotný reopened an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matěj Novotný Resolution: Rejected Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matěj Novotný Fix Version/s: 3.1.5.Final Fix Version/s: 4.0.0.Alpha4 Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Tassilo karge commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Created pull request: https://github.com/weld/core/pull/2003 Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Tassilo karge commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Sure! In fact I already fixed it locally. It is not an eclipse-only feature though. There is an IntelliJ plugin called SmartTomcat (https://plugins.jetbrains.com/plugin/9492-smart-tomcat) which deploys applications in the same way. It is a little difficult to find the culprit, though, so I guess most people just give up and use the slower way of packing everything into a WAR and deploying it in that way. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matěj Novotný commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Hi Tassilo karge, this is an Eclipse-only feature which also had a workaround mentioned, the issue was rejected so no fixing was planned. I am not strictly against this even though I don't see this being used much. So if you want to step up and contribute a fix (against 3.1 branch), please go ahead. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Tassilo karge commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Is there a plan to have a fix in a future version? I would like to weigh in on a fix of this issue. The WebAppBeanArchiveScanner does not do appropriate equality checks on the paths it discovers in two different ways. When a server.xml (admittedly NOT deployed via a WAR) specifies a resource directory like this (replace ... with a custom path): ```xml ``` the DefaultBeanArchiveScanner returns `C:\...\target\classes\META-INF\beans.xml` as one of the beans paths. Afterwards, the WebAppBeanArchiveScanner does substring matching to determine whether the path contains `WEB-INF\classes` (which the path does not). It then asks the servelet context for the beans.xml resource in the server´s `WEB-INF\classes\META-INF` directory, and resolves it to the real file url which is again `C:\...\target\classes\META-INF\beans.xml`. Thus, the same resource is found twice. The problem is that substring matching is used to determine whether two semantically different URLs are the same. One of the URLs is the logical path to the file from the server´s view and one is the real path to the file. A simple fix to the issue would be to perform the path comparison after the real file path of the beans.xml was resolved. However, I am not sure whether it would match with the specification to, since I do not know the relevant part. Add Comment This message was sent by Atlassian Jira (v7.13.8#713008-sha1:1606a5c) ___ 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 Matej Novotny resolved as Rejected Rejecting issue. This is about a custom deployment model that we do not support in a backward portable fashion. There is still a way to make it fully functional with newer versions of Weld and Tomcat, the only problem is with Weld 1 which is no longer actively developed. Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matej Novotny Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing
[weld-issues] [JBoss JIRA] (WELD-2570) WELD-ENV-000033 error using Tomcat 8+ in Eclipse
Title: Message Title Matej Novotny updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matej Novotny Fix Version/s: 3.1.x 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 Matej Novotny commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in 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. I see, this explains it. The structure of files is then very different to what Weld expects from an actual archive (WAR). This Eclipse feature was never supported, at least not intentionally. I'd say that since you can make it work for newer Weld & Tomcat versions and Weld 1 is no longer being developed, we can close this issue. 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-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
Matej Novotny edited a comment on WELD-2570
Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse
Looking at docs for older version (Weld 1), I can see following:bq. That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). So I am quite surprised that it worked for you before on Tomcat 7 with Weld 1 under {{META-INF}}.When you are deploying via IDE, what does the deployment look like? It is an actual WAR at all? If it's not, then Weld might be going a different way in discovering {{beans.xml}} perhaps.Also noteworthy is that you are comparing Weld 1 and Weld 3 in this regards and there are likely some differences in this, especially given that servlet support isn't rooted in CDI spec at all.
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 Matej Novotny updated an issue Weld / WELD-2570 WELD-ENV-33 error using Tomcat 8+ in Eclipse Change By: Matej Novotny Fix Version/s: 3.1.x 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 Matej Novotny commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Looking at docs for older version (Weld 1), I can see following: That means each archive that contains beans must include a file named beans.xml in the META-INF directory of the classpath or WEB-INF directory of the web root (for war archives). So I am quite surprised that it worked for you before on Tomcat 7 with Weld 1 under META-INF. When you are deploying via IDE, what does the deployment look like? It is an actual WAR at all? 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 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 Matej Novotny commented on WELD-2570 Re: WELD-ENV-33 error using Tomcat 8+ in Eclipse Hello Carlos Aristu according to Weld specification, you should have your beans.xml under WEB-INF folder for WAR archives. See this bit of the documentation. Is there a specific reason why you cannot adhere to that? Having it in WEB-INF should rule out what default scanner finds. 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. I am afraid I don't see how beans.xml placement depends on how you deploy the application? It should simply be packaged inside the WAR you are deploying, therefore it is in place before you get to deploying. 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 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 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. 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 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 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.
