[weld-issues] [JBoss JIRA] (CDITCK-436) tests with @ShouldThrowException in Extensions must not later try to use the BeanManager
Title: Message Title Mark Struberg commented on CDITCK-436 Re: tests with @ShouldThrowException in Extensions must not later try to use the BeanManager indeed this fixed our issue! Txs for the pointer! Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-436) tests with @ShouldThrowException in Extensions must not later try to use the BeanManager
Title: Message Title Tomas Remes closed an issue as Resolved at Apache CDI TCK / CDITCK-436 tests with @ShouldThrowException in Extensions must not later try to use the BeanManager Change By: Tomas Remes Status: Open Closed Resolution: Resolved at Apache Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1456) ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification
Title: Message Title Marcial Atiénzar Navarro commented on WELD-1456 Re: ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification I'm using wildfly 8.1.0-Final, and when deploying a webapp and access firefox to test it, I've this error: Mensaje: WELD-001456: Argument resolvedBean must not be null Traza: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: Argument resolvedBean must not be null at org.jboss.weld.util.Preconditions.checkArgumentNotNull(Preconditions.java:40) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:766) at org.jboss.weld.injection.ParameterInjectionPointImpl.getValueToInject(ParameterInjectionPointImpl.java:76) at org.jboss.weld.injection.ConstructorInjectionPoint.getParameterValues(ConstructorInjectionPoint.java:138) at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:68) at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28) at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:85) at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:183) at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.createAndInjectBeans(DestructibleBeanInstance.java:53) at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.(DestructibleBeanInstance.java:33) at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createInstance(ValidatorFactoryBean.java:206) at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createConstraintValidatorFactory(ValidatorFactoryBean.java:192) at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:119) at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:52) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:99) at org.jboss.weld.proxies.ValidatorFactory$627848863$Proxy$_$$_WeldClientProxy.getMessageInterpolator(Unknown Source) at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getMessageInterpolator(LazyValidatorFactory.java:101) at org.jboss.resteasy.plugins.validation.GeneralValidatorImpl.getValidator(GeneralValidatorImpl.java:559) at org.jboss.resteasy.plugins.validation.GeneralValidatorImpl.validate(GeneralValidatorImpl.java:69) at org.jboss.resteasy.cdi.JaxrsInjectionTarget.validate(JaxrsInjectionTarget.java:108) at org.jboss.resteasy.cdi.JaxrsInjectionTarget.inject(JaxrsInjectionTarget.java:69) at org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:109) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.j
[weld-issues] [JBoss JIRA] (WELD-1456) ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification
Title: Message Title Marcial Atiénzar Navarro updated an issue Weld / WELD-1456 ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification This the interface that produces the error. It's package on a jar inside WEB-INF/lib of all webapps deployed on server. Only one webapp has the implementation. I need this interface on a jar to access to generate code on others webapps. Change By: Marcial Atiénzar Navarro Attachment: IParametroWS.java Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1456) ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification
Title: Message Title Marcial Atiénzar Navarro commented on WELD-1456 Re: ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification May be it relationated with this: RESTEASY-1082 Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1456) ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification
Title: Message Title Jozef Hartinger commented on WELD-1456 Re: ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification Marcial Atiénzar Navarro please create a new issue for your problem Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-438) InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
Title: Message Title Antoine Sabot-Durand commented on CDITCK-438 Re: InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml This test is not about Interceptor but about wrong meta-data injection in interceptor. Injection of Interceptor in InterceptorField (instead of Interceptor is what is tested. And it does the job. The spec is rather clear regarding the fact that Interceptors are bean in implicit terms here : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans or in more explicit way in this the recent clarification : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations It is said nowhere that unused interceptor or decorators should be ignored by the container. Now that can be discussed but doesn't seem very interesting IMO. Anyway this ticket is off topic and misleading. Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-438) InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
Title: Message Title
Antoine Sabot-Durand edited a comment on CDITCK-438
Re: InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
This test is not about Interceptor activation but about wrong meta-data injection in interceptor. Injection of {{Interceptor}} in {{InterceptorField}} (instead of {{Interceptor}} ) is what is tested. And it does the job by throwinf a definition exception as stated here : http://docs . jboss.org/cdi/spec/1.2/cdi-spec.html#bean_metadata. The spec is rather clear regarding the fact that Interceptors are bean in implicit terms here : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans or in more explicit way in this the recent clarification : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotationsIt is said nowhere that unused interceptor or decorators should be ignored by the container. Now that can be discussed but doesn't seem very interesting IMO.Anyway this ticket is off topic and misleading.
Add Comment
This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1456) ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification
Title: Message Title Marcial Atiénzar Navarro commented on WELD-1456 Re: ProgrammaticallyAddedProcessBeanAttributesTest should only test built-in beans explicitly listed in the specification Sorry, I thought it was related to this issue. Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-438) InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
Title: Message Title
Antoine Sabot-Durand edited a comment on CDITCK-438
Re: InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
This test is not about Interceptor activation but about wrong meta-data injection in interceptor. Injection of {{Interceptor}} in {{InterceptorField}} (instead of {{Interceptor}}) is what is tested. And it does the job by throwinf a definition exception as stated here : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_metadata.The spec is rather clear regarding the fact that Interceptors are bean in implicit terms here : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#what_classes_are_beans or in more explicit way in this the recent clarification : http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations It is said nowhere that unused interceptor or decorators should be ignored by the container. Now that can be discussed but doesn , as it ' t seem s not very interesting IMO.Anyway this ticket is off topic to test unused Interceptors or Decoractors and misleading as the expected behaviour will be the same with these activated, we could add {{@Priority}} to the faulty Interceptors / Decorators without changing the nature of what is tested .
Add Comment
This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1728) Prototype: Ordered events
Title: Message Title Jozef Hartinger assigned an issue to Martin Kouba Weld / WELD-1728 Prototype: Ordered events Change By: Jozef Hartinger Assignee: Martin Kouba Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-438) InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml
Title: Message Title Jozef Hartinger commented on CDITCK-438 Re: InterceptorTypeParamFieldTest must either use @Priority or add the interceptors to beans.xml I filed CDI-459 for spec clarification. Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1737) Improve javadoc for org.jboss.weld.event.ObserverNotifier
Title: Message Title Martin Kouba created an issue Weld / WELD-1737 Improve javadoc for org.jboss.weld.event.ObserverNotifier Issue Type: Enhancement Affects Versions: 2.2.4.Final Assignee: Unassigned Created: 08/Sep/14 9:37 AM Priority: Minor Reporter: Martin Kouba Add description for public methods with duplicit names but different behaviour (fireEvent, resolveObserverMethods, buildEventResolvable, etc.) Add Comment
[weld-issues] [JBoss JIRA] (WELD-1726) Isolate Weld SE/Servlet logging into message logger interfaces
Title: Message Title Kirill Gaevskii updated WELD-1726 Weld / WELD-1726 Isolate Weld SE/Servlet logging into message logger interfaces Change By: Kirill Gaevskii Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/646#issuecomment-54779683 Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1728) Prototype: Ordered events
Title: Message Title Martin Kouba commented on WELD-1728 Re: Prototype: Ordered events A simple prototype (work in progress, no optimizations, etc.) is here: https://github.com/mkouba/core/tree/WELD-1728 Observations: @javax.annotation.Priority target would have to be updated, it's @Target(TYPE) atm the spec would have to define a way to specify priority for custom observers this prorotype defines an optional interface org.jboss.weld.experimental.Prioritized observer methods without @Priority are called after prioritized observers, other possibility would be to set the default priority to some predefined constant a la javax.interceptor.Interceptor.Priority.APPLICATION transactional observers notifications are "grouped" into single JTA synchronization note that there are three possible "ordered batches" of deffered notifications: BEFORE_COMPLETION (if we try to commit the tx) AFTER_COMPLETION + AFTER_FAILURE (if tx rolled back) AFTER_COMPLETION + AFTER_SUCCESS (if tx commited) see also org.jboss.weld.event.TransactionNotificationSynchronization Add Comment
[weld-issues] [JBoss JIRA] (WELD-1677) BeanAttributes.getTypes() returns also canonical types
Title: Message Title Jozef Hartinger updated WELD-1677 Weld / WELD-1677 BeanAttributes.getTypes() returns also canonical types Change By: Jozef Hartinger Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1723) Injection of parameterized types does not longer work in 2.x (starting with 2.0.0.Alpha3)
Title: Message Title Jozef Hartinger updated WELD-1723 Weld / WELD-1723 Injection of parameterized types does not longer work in 2.x (starting with 2.0.0.Alpha3) Change By: Jozef Hartinger Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.3.1#6329-sha1:7df76f1) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
