[weld-issues] [JBoss JIRA] (WELD-2236) Document the usage of org.jboss.weld.environment.Container.CONTEXT_PARAM_CONTAINER_CLASS
Title: Message Title Martin Kouba created an issue Weld / WELD-2236 Document the usage of org.jboss.weld.environment.Container.CONTEXT_PARAM_CONTAINER_CLASS Issue Type: Task Assignee: Unassigned Components: Documentation, Servlet Container Support Created: 15/Sep/16 9:32 AM Fix Versions: 2.4.1.Final, 3.0.0.Beta1 Priority: Major Reporter: Martin Kouba Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Martin Kouba resolved as Rejected Weld / WELD-2235 Avoid nasty stacktrace when Change By: Martin Kouba Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Martin Kouba commented on WELD-2235 Re: Avoid nasty stacktrace when Well, Weld is looking for org.apache.catalina.connector.Request class which is part of Tomcat core. Also the result of camel/examples/camel-example-cdi-rest-servlet$ mvn dependency:tree | grep tomcat is: [INFO] | +- org.apache.tomcat.embed:tomcat-embed-core:jar:8.5.0:runtime [INFO] | \- org.apache.tomcat.embed:tomcat-embed-jasper:jar:8.5.0:runtime [INFO] | +- org.apache.tomcat.embed:tomcat-embed-el:jar:8.5.0:runtime So it seems the bad dependecy was not jasper, but tomcat-embed-core. Anyway, I'm glad it works for you now . Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Claus Ibsen commented on WELD-2235 Re: Avoid nasty stacktrace when Feel free to close/reject the ticket as its a user mistake. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Claus Ibsen edited a comment on WELD-2235 Re: Avoid nasty stacktrace when Hi MartinThanks I found out there was a tomcat-jasper JAR by mistake that causes this. Removed it deprecated and Weld detects Jetty only , and there is no stacktraces/errors anymore: 2016-09-15 15:15:05,453 [main ] INFO servletJetty - WELD-ENV-001200: Jetty 7.2+ detected, CDI injection will be available in Servlets and Filters. Injection into Listeners should work on Jetty 9.1.1 and newer.Maybe that is an uncommon mistake? But some servers uses Jasper JSP compiler from Tomcat and thus it may confuse WELD what server you use. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Claus Ibsen commented on WELD-2235 Re: Avoid nasty stacktrace when Hi Martin Thanks I found out there was a tomcat-jasper JAR by mistake that causes this. Removed it deprecated Jetty only 2016-09-15 15:15:05,453 [main ] INFO servletJetty - WELD-ENV-001200: Jetty 7.2+ detected, CDI injection will be available in Servlets and Filters. Injection into Listeners should work on Jetty 9.1.1 and newer. Maybe that is an uncommon mistake? But some servers uses Jasper JSP compiler from Tomcat and thus it may confuse WELD what server you use. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Martin Kouba commented on WELD-2235 Re: Avoid nasty stacktrace when Hi Claus, it seems you have Tomcat classes on classpath - that's why Weld attempts to initialize some Tomcat integration components. In such cases, the best thing to do is to manually set the servlet container type - use org.jboss.weld.environment.container.class context parameter and set it to org.jboss.weld.environment.jetty.JettyContainer. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Martin Kouba updated an issue Weld / WELD-2235 Avoid nasty stacktrace when Change By: Martin Kouba Component/s: Servlet Container Support Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2235) Avoid nasty stacktrace when
Title: Message Title Claus Ibsen created an issue Weld / WELD-2235 Avoid nasty stacktrace when Issue Type: Enhancement Affects Versions: 2.4.0.Final Assignee: Unassigned Created: 15/Sep/16 8:57 AM Priority: Minor Reporter: Claus Ibsen When we run the Apache Camel example with Weld, CDI and Jetty, we see this exception 2016-09-15 14:54:46,451 [main ] ERROR servletTomcat - WELD-ENV-001102: Unable to replace Tomcat 7 AnnotationProcessor. CDI injection will not be available in Servlets, Filters, or Listeners. java.lang.RuntimeException: WELD-ENV-001104: Cannot get StandardContext from ServletContext. at
[weld-issues] [JBoss JIRA] (WELD-2223) Registering servlet listener on tomcat embedded fails
Title: Message Title Martin Kouba resolved as Rejected Weld / WELD-2223 Registering servlet listener on tomcat embedded fails Change By: Martin Kouba Status: Reopened Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2234) HttpSessionContext.destroy(Contextual contextual) should always check the underlying HttpSession
Title: Message Title Martin Kouba created an issue Weld / WELD-2234 HttpSessionContext.destroy(Contextual contextual) should always check the underlying HttpSession Issue Type: Bug Assignee: Unassigned Components: Scopes & Contexts Created: 15/Sep/16 8:07 AM Fix Versions: 2.4.1.Final, 3.0.0.Beta1 Priority: Major Reporter: Martin Kouba Right now, AttributeBeanStore.remove(BeanIdentifier) does not remove a bean instance created in a different HTTP request. See also http://lists.jboss.org/pipermail/weld-dev/2016-September/003487.html. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2233) CDI Implicit bean archive not supported in Java SE
Title: Message Title Antoine Sabot-Durand closed an issue as Won't Fix Weld / WELD-2233 CDI Implicit bean archive not supported in Java SE Change By: Antoine Sabot-Durand Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2233) CDI Implicit bean archive not supported in Java SE
Title: Message Title Antoine Sabot-Durand commented on WELD-2233 Re: CDI Implicit bean archive not supported in Java SE Sorry, I missed section 15.1 in the spec... So it's not Weld related and is more a clarification needed between core and SE in the spec. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2233) CDI Implicit bean archive not supported in Java SE
Title: Message Title Martin Kouba commented on WELD-2233 Re: CDI Implicit bean archive not supported in Java SE Antoine Sabot-Durand Do you have "implicit scan" enabled? AFAIK this functionlity should be disabled by default (due to potential performance problems). In Weld, you could either use org.jboss.weld.se.scan.classpath.entries (as described in http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#_implicit_bean_archive_support_2) or javax.enterprise.inject.scan.implicit (as described in https://docs.jboss.org/cdi/spec/2.0.EDR2/cdi-spec.html#bean_archive_se) to enabled this functionality. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2233) CDI Implicit bean archive not supported in Java SE
Title: Message Title Antoine Sabot-Durand created an issue Weld / WELD-2233 CDI Implicit bean archive not supported in Java SE Issue Type: Bug Affects Versions: 3.0.0.Alpha17 Assignee: Unassigned Components: Java SE Support Created: 15/Sep/16 6:40 AM Priority: Major Reporter: Antoine Sabot-Durand When using an implicit bean archive (without beans.xml but with classes having bean defining annotation), those beans are not discovered. This is either a bug in Weld or in CDI spec, since implicit bean archive is defined in core part of the spec and should work in SE as in EE. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2232) JandexClassFileServices should probably throw ClassFileInfoException if unable to load annotation
Title: Message Title Martin Kouba updated an issue Weld / WELD-2232 JandexClassFileServices should probably throw ClassFileInfoException if unable to load annotation Change By: Martin Kouba Fix Version/s: 2.4.1.Final Fix Version/s: 3.0.0.Beta1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2232) JandexClassFileServices should probably throw ClassFileInfoException if unable to load annotation
Title: Message Title Martin Kouba created an issue Weld / WELD-2232 JandexClassFileServices should probably throw ClassFileInfoException if unable to load annotation Issue Type: Bug Assignee: Unassigned Components: Java SE Support, Servlet Container Support Created: 15/Sep/16 4:19 AM Priority: Minor Reporter: Martin Kouba Currently, an IllegalStateException is thrown and the container initialization is aborted. Add Comment
