[weld-issues] [JBoss JIRA] (WELD-1658) bean-discovery-mode=annotated support and isolated bean archives in Weld Servlet
Martin Kouba assigned WELD-1658 to Martin Kouba bean-discovery-mode=annotated support and isolated bean archives in Weld Servlet Change By: Martin Kouba (22/Apr/14 3:24 AM) Assignee: MartinKouba This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1601) Lifecycle and session not initialized with portlets
Jozef Hartinger updated WELD-1601 Lifecycle and session not initialized with portlets Change By: Jozef Hartinger (22/Apr/14 3:35 AM) Status: PullRequestSent Resolved Resolution: Done This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-266) Create clustering (functional) tests from Weld examples
Jozef Hartinger resolved WELD-266 as Done Create clustering (functional) tests from Weld examples Already implemented. Change By: Jozef Hartinger (22/Apr/14 3:40 AM) Status: Open Resolved Resolution: Done This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1659) Optimize use of proxies for reference injection
Jozef Hartinger created WELD-1659 Optimize use of proxies for reference injection Issue Type: Task Assignee: Martin Kouba Components: Proxies Created: 22/Apr/14 4:41 AM Description: The spec allows the following optimization to be put in place: For certain combinations of scopes, the container is permitted to optimize the above procedure: The container is permitted to directly inject a contextual instance of the bean, as defined in Section 6.5.2. If an incompletely initialized instance of the bean is registered with the current CreationalContext, as defined in Section 6.1, the container is permitted to directly inject this instance. However, in performing these optimizations, the container must respect the rules of injectable reference validity. Start by enumerating the set of allowed combinations of scopes. Project: Weld Priority: Major Reporter: Jozef Hartinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1615) org.jboss.weld.environment.servlet.Listener crashes in GWT dev hosted mode
Tomek D commented on WELD-1615 org.jboss.weld.environment.servlet.Listener crashes in GWT dev hosted mode Sure. I will try it this week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1659) Optimize use of proxies for reference injection
Martin Kouba edited a comment on WELD-1659 Optimize use of proxies for reference injection The scope of a bean \ The scope of a bean eligible for injection Request Session Application Conversation Request OK OK OK OK Session X X X X Application X X OK X Conversation X X X X This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-410) some tests fail with Java8
Mark Struberg created CDITCK-410 some tests fail with Java8 Issue Type: Bug Assignee: Martin Kouba Created: 22/Apr/14 7:49 AM Description: The following tests fail with Java8: org.jboss.jsr299.tck.tests.event.observer.conditional.ConditionalObserverTest org.jboss.jsr299.tck.tests.implementation.disposal.method.definition.DisposalMethodDefinitionTest The underlying problem is that java8 returns getMethods() in a different order now. And those 2 tests really depend on the order they are executed in. The first test method e.g. notifies a Bean which has an IF_EXIST observer method and later asserts that the observer method did not get triggered. But this test method fails if the other test-methods of the class got executed before it (because of the different method ordering in Java8). Project: CDI TCK Priority: Major Reporter: Mark Struberg Security Level: Public (Everyone can see) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-410) some tests fail with Java8
Martin Kouba updated CDITCK-410 some tests fail with Java8 Change By: Martin Kouba (22/Apr/14 7:51 AM) Assignee: MartinKouba TomasRemes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1660) Registering alternative during AfterTypeDiscovery event fails with NPE
Tomas Remes
created WELD-1660
Registering alternative during AfterTypeDiscovery event fails with NPE
Issue Type:
Bug
Assignee:
Jozef Hartinger
Created:
22/Apr/14 8:05 AM
Description:
Following code fails with NPE, because the priority is null in org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder#getGlobalAlternativeMap
public void afterTypeDiscovery(@Observes AfterTypeDiscovery event) {
event.getAlternatives().add(IntegerBean.class);
}
Stacktrace:
13:54:10,245 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC01: Failed to start service jboss.deployment.unit."4ded9a73-c1a8-48b2-b884-ec631181e7b3.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."4ded9a73-c1a8-48b2-b884-ec631181e7b3.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NullPointerException: null value in entry: class org.jboss.cdi.tck.tests.definition.bean.custom.IntegerBean=null
at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33)
at com.google.common.collect.SingletonImmutableBiMap.init(SingletonImmutableBiMap.java:39)
at com.google.common.collect.ImmutableBiMap.of(ImmutableBiMap.java:57)
at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:80)
at com.google.common.collect.ImmutableMap.copyOf(ImmutableMap.java:292)
at org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder.getGlobalAlternativeMap(GlobalEnablementBuilder.java:193)
at org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder.createModuleEnablement(GlobalEnablementBuilder.java:236)
at org.jboss.weld.bootstrap.BeanDeployment.createEnablement(BeanDeployment.java:219)
at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:363)
at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
... 3 more
Project:
Weld
Priority:
Major
Reporter:
Tomas Remes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1660) Registering alternative during AfterTypeDiscovery event fails with NPE
Jozef Hartinger updated WELD-1660 Registering alternative during AfterTypeDiscovery event fails with NPE Change By: Jozef Hartinger (22/Apr/14 8:30 AM) Fix Version/s: 2.2.1.Final This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1661) Consider possible code clean-up
Tomas Remes created WELD-1661 Consider possible code clean-up Issue Type: Enhancement Affects Versions: 2.2.0.SP1 Assignee: Jozef Hartinger Created: 22/Apr/14 9:01 AM Description: I've gone through the Weld code coverage report (including TCK, tests, arquillian tests) and discovered bunch of likely useless (not called) classes and some pieces of code. Classes are: org.jboss.weld.bootstrap.ExtensionBeanDeployerEnvironment org.jboss.weld.context.ForwardingWeldCreationalContext org.jboss.weld.context.beanstore.ForwardingNamingScheme org.jboss.weld.context.beanstore.http.LazyCyclicSessionBeanStore org.jboss.weld.exceptions.NullableDependencyException org.jboss.weld.executor.TaskPerItemTaskFactory org.jboss.weld.injection.ForwardingInjectionTarget org.jboss.weld.interceptor.util.InterceptorMetadataException org.jboss.weld.manager.RemoveMetadataWrapperFunction org.jboss.weld.resolution.ForwardingInterceptorResolvable org.jboss.weld.resources.SharedObjectFacade org.jboss.weld.serialization.NoopSerializableHolder org.jboss.weld.util.annotated.ForwardingAnnotatedConstructor org.jboss.weld.util.annotated.ForwardingAnnotatedField org.jboss.weld.util.annotated.ForwardingAnnotatedParameter org.jboss.weld.util.annotated.ForwardingWeldAnnotation org.jboss.weld.util.annotated.ForwardingWeldConstructor org.jboss.weld.util.annotated.ForwardingWeldField org.jboss.weld.util.annotated.ForwardingWeldMember (called, but only in classes mentioned in this list) org.jboss.weld.util.annotated.ForwardingWeldMethod org.jboss.weld.util.annotated.ForwardingWeldParameter org.jboss.weld.util.collections.ArrayListSupplier org.jboss.weld.util.collections.ArraySetSupplier org.jboss.weld.util.collections.ConcurrentHashSetSupplier org.jboss.weld.util.collections.CopyOnWriteArrayListSupplier org.jboss.weld.util.collections.DefaultValueMap org.jboss.weld.util.collections.SetView org.jboss.weld.util.dom.NodeListIterable org.jboss.weld.util.dom.NodeListIterator (called in the class above only) org.jboss.weld.util.reflection.ClassLoaderFunction Following pieces of code could be likely also removed: org.jboss.weld.injection.DynamicInjectionPoint#DynamicInjectionPoint(org.jboss.weld.injection.SLSBInvocationInjectionPoint, java.lang.String) org.jboss.weld.injection.DynamicInjectionPoint#readResolve org.jboss.weld.util.Beans#findInterceptorBindingConflicts - not sure but I guess the if statement is useless in for cycle org.jboss.weld.util.bean.WrappedBeanHolder - this class is used in static classes, which are not likely referenced anywhere. org.jboss.weld.util.bytecode.DescriptorUtils#descriptorStringToParameterArray org.jboss.weld.util.bytecode.DescriptorUtils#isWide(java.lang.Class?) org.jboss.weld.util.bytecode.DescriptorUtils#getConstructorDescriptor org.jboss.weld.util.bytecode.DescriptorUtils#getMethodDescriptor(java.lang.reflect.Method) All changes are available https://github.com/tremes/core/commit/6e7a4595d8b1cf4eaf1dee9a8924c4f1ee9e0cd2, but I still need to test it properly. Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1452) Conversation timeout in redirect
RH Bugzilla Integration updated WELD-1452 Conversation timeout in redirect Change By: RH Bugzilla Integration (22/Apr/14 10:17 AM) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1070069,https://bugzilla.redhat.com/show_bug.cgi?id=1088791 ,https://bugzilla.redhat.com/show_bug.cgi?id=1089990 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1657) Backport WELD-1452
RH Bugzilla Integration updated WELD-1657 Backport WELD-1452 Change By: RH Bugzilla Integration (22/Apr/14 10:17 AM) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1070069 ,https://bugzilla.redhat.com/show_bug.cgi?id=1089990 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1657) Backport WELD-1452
RH Bugzilla Integration commented on WELD-1657 Backport WELD-1452 Jozef Hartinger jhart...@redhat.com changed the Status of bug 1089990 from NEW to POST This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1452) Conversation timeout in redirect
RH Bugzilla Integration commented on WELD-1452 Conversation timeout in redirect Jozef Hartinger jhart...@redhat.com changed the Status of bug 1089990 from NEW to POST This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1657) Backport WELD-1452
RH Bugzilla Integration updated WELD-1657 Backport WELD-1452 Change By: RH Bugzilla Integration (22/Apr/14 11:48 AM) Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1070069,https://bugzilla.redhat.com/show_bug.cgi?id=1089990 ,https://bugzilla.redhat.com/show_bug.cgi?id=1088791 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
