[weld-issues] [JBoss JIRA] (WELD-2630) Publish a Milestone version of Weld-servlet-core
Title: Message Title Arjan Tijms commented on WELD-2630 Re: Publish a Milestone version of Weld-servlet-core For those interested in testing with Piranha, I did a quick patched version here. The patched version simply removed the Tomcat, Jetty and GWT containers: https://github.com/omnifaces/omni-weld-servlet-core I added this to Piranha and at least the initial build works, but need to test more to see if everything really works. 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-2630) Publish a Milestone version of Weld-servlet-core
Title: Message Title Matěj Novotný edited a comment on WELD-2630 Re: Publish a Milestone version of Weld-servlet-core Some notes to self: * Arquillian servlet protocol will need to be updated for any testing to work, see [https://github.com/arquillian/arquillian-core/issues/248] * * And we will also need new Arq. adapters for Tomcat (and later jetty), there is already an [issue|https://github.com/arquillian/arquillian-container-tomcat/issues/86] created for it but it needs to first consume the new servlet protocol * Jetty has some alpha0 release of version 11 which seems to be using EE 9, we should look into that as well 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
