[weld-issues] [JBoss JIRA] (CDITCK-416) Extend tests for BeanAttributes#getTypes() with generic scenario
Title: Message Title
Matus Abaffy edited a comment on CDITCK-416
Re: Extend tests for BeanAttributes#getTypes() with generic scenario
*UPDATE: Yes, that seems to be it. The thing is that if a class A (or interface) extends a raw type of a generic class (class MyRawBean extends MyBean; class MyBean), than there "are no generics" in the type hierarchy of the class A, i.e. only raw versions of generic supertypes are supertypes of the class A (MySuperInterface instead of MySuperInterface).I did not find (did not even search) where this behavior is defined. I detected the behavior with these steps:https://bugs.eclipse.org/bugs/show_bug.cgi?id=437511 - I remember that Eclipse editor could not detect this and did not warn me, so I filed an issue.For "definition", see Stephan's comment.(And to raise the priority of the issue, just verify that Eclipse compiles it without problems. :) I am forced to use IDEA now.)Another case:{code}public interface MyGenericInterface>{code}{code}public class MyGenericBean implements MyGenericInterface{code}In IntelliJ IDEA, it shows me a problem "Type parameter 'T' is not within its bounds; should implement MySuperInterface" which means that MyRawBean is not (considered to be) a subtype of MyGenericInterface.
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-416) Extend tests for BeanAttributes#getTypes() with generic scenario
Title: Message Title Matus Abaffy commented on CDITCK-416 Re: Extend tests for BeanAttributes#getTypes() with generic scenario The thing is that if a class A (or interface) extends a raw type of a generic class (class MyRawBean extends MyBean; class MyBean), than there "are no generics" in the type hierarchy of the class A, i.e. only raw versions of generic supertypes are supertypes of the class A (MySuperInterface instead of MySuperInterface). I did not find (did not even search) where this behavior is defined. I detected the behavior with these steps: https://bugs.eclipse.org/bugs/show_bug.cgi?id=437511 - I remember that Eclipse editor could not detect this and did not warn me, so I filed an issue. For "definition", see Stephan's comment. (And to raise the priority of the issue, just verify that Eclipse compiles it without problems. I am forced to use IDEA now.) Another case: public interface MyGenericInterfaceextends MySuperInterface> public class MyGenericBeanextends MyRawBean> implements MyGenericInterface In IntelliJ IDEA, it shows me a problem "Type parameter 'T' is not within its bounds; should implement MySuperInterface" which means that MyRawBean is not (considered to be) a subtype of MyGenericInterface. 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-416) Extend tests for BeanAttributes#getTypes() with generic scenario
Title: Message Title Matus Abaffy commented on CDITCK-416 Re: Extend tests for BeanAttributes#getTypes() with generic scenario The tests in PR should pass now. Can someone verify that and merge the PR? 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-257) Formalize support for GAE including tests
Title: Message Title Matus Abaffy commented on WELD-257 Re: Formalize support for GAE including tests As GAE uses Jetty 6 and Weld does not support Jetty 6 anymore, this doesn't seem to be supported in the foreseeable future. Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-257) Formalize support for GAE including tests
Title: Message Title Matus Abaffy updated an issue Weld / WELD-257 Formalize support for GAE including tests Change By: Matus Abaffy Assignee: Matus Abaffy Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1518) IllegalStateException after CrossContextForwardTest
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1518 IllegalStateException after CrossContextForwardTest Change By: Matus Abaffy Assignee: Matus Abaffy Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1697) Make context id configurable with Weld Servlet
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1697 Make context id configurable with Weld Servlet Change By: Matus Abaffy Assignee: Matus Abaffy Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-384) Create tests for observer method invocation context
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-384 Create tests for observer method invocation context Change By: Matus Abaffy Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/76 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-414 Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds Change By: Matus Abaffy Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/75 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1693) Warn if a managed bean class is annotated as a session bean
Title: Message Title
Matus Abaffy created an issue
Weld / WELD-1693
Warn if a managed bean class is annotated as a session bean
Issue Type:
Feature Request
Affects Versions:
2.2.1.Final
Assignee:
Unassigned
Components:
Class Beans (Managed and Session)
Created:
12/Jun/14 6:15 AM
Priority:
Minor
Reporter:
Matus Abaffy
Security Level:
Public (Everyone can see)
It can happen that a managed bean class has a session bean annotation (e.g. @Stateless) when the class does not satisfy the requirements for the session bean class (see EJB spec., 4.9.2 Session Bean Class).
For example, the following class is a managed bean as it is not public:
@Stateless
class Foo {}
However, a warning should be r
[weld-issues] [JBoss JIRA] (WELD-1693) Warn if a managed bean class is annotated as a session bean
Title: Message Title
Matus Abaffy updated an issue
Weld / WELD-1693
Warn if a managed bean class is annotated as a session bean
Change By:
Matus Abaffy
It can happen that a managed bean class has a session bean annotation (e.g. @Stateless) when the class does not satisfy the requirements for the session bean class (see EJB 3.2 spec., 4.9.2 Session Bean Class).For example, the following class is a managed bean as it is not public:{code}@Statelessclass Foo {}{code}However, a warning should be raised by the application server at the first place.
Add Comment
This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1691) SessionBean ID not unique
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1691 SessionBean ID not unique Change By: Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/597 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1691) SessionBean ID not unique
Title: Message Title Matus Abaffy assigned an issue to Matus Abaffy Weld / WELD-1691 SessionBean ID not unique Change By: Matus Abaffy Assignee: Matus Abaffy Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-411) Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e)
Title: Message Title Matus Abaffy resolved as Duplicate Issue Closing in favor of CDITCK-414. CDI TCK / CDITCK-411 Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e) Change By: Matus Abaffy Status: Open Resolved Resolution: Duplicate Issue Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-411) Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e)
Title: Message Title Matus Abaffy closed an issue as Duplicate Issue CDI TCK / CDITCK-411 Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e) Change By: Matus Abaffy Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-414 Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds Change By: Matus Abaffy Test bean assignability regarding parameterized type with :- type variable(s) with multiple bounds . - wildcard with type variable(s) with multiple bounds as its lower bound Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-414 Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds Change By: Matus Abaffy Summary: Create tests regarding WELD-1671 bean assignability of parameterized type with type variable(s) with multiple bounds Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1689) InjectionServices.aroundInject() called twice
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1689 InjectionServices.aroundInject() called twice Change By: Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/594 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-420) InterceptorModularityTest is not portable
Title: Message Title Matus Abaffy resolved as Done CDI TCK / CDITCK-420 InterceptorModularityTest is not portable Change By: Matus Abaffy Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1684) BeanTypeAssignabilityRules#matches is incorrect for TypeVariable with multiple bounds
Title: Message Title Matus Abaffy created an issue Weld / WELD-1684 BeanTypeAssignabilityRules#matches is incorrect for TypeVariable with multiple bounds Issue Type: Bug Affects Versions: 2.2.1.Final Assignee: Matus Abaffy Created: 27/May/14 8:59 AM Fix Versions: 2.2.2.Final Priority: Major Reporter: Matus Abaffy The current implementation assumes a TypeVariable has at most one bound, which leads to incorrect injection point resolution. Revise usages of EventTypeAssignabilityRules#areTypesInsideBounds and EventTypeAssignabilityRules#isTypeInsideBounds. Add Comment
[weld-issues] [JBoss JIRA] (CDITCK-420) InterceptorModularityTest is not portable
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-420 InterceptorModularityTest is not portable Change By: Matus Abaffy Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/71 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1572) Validating interceptors of a bean which declares a passivating scope uses the bean's bean manager instead of interceptor's BM
Title: Message Title
Matus Abaffy updated an issue
Weld / WELD-1572
Validating interceptors of a bean which declares a passivating scope uses the bean's bean manager instead of interceptor's BM
Change By:
Matus Abaffy
When validating whether a bean is passivation capable, org.jboss.weld.bootstrap.Validator uses the bean's bean manager for validating injection points of its interceptors, which can result in incorrect exception due to ambiguous dependency:{code}org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318: Cannot resolve an ambiguous dependency between: - Managed Bean [class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Dog] with qualifiers [@Any @Default], - Managed Bean [class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Cat] with qualifiers [@Any @Default] at org.jboss.weld.manager.BeanManagerImpl.resolve(BeanManagerImpl.java:1181) at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:221) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:504) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_17] ... 3 more{code}-> Class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Cat is not (required to be) accessible to the module containing the interceptor class with injection point causing this exception.Test case: https://github org . com/bafco/ jboss. cdi - . tck /tree/beanAccessibility .tests.lookup.modules.interceptors.InterceptorModularityTest
Add Comment
This message w
[weld-issues] [JBoss JIRA] (CDITCK-416) Extend tests for BeanAttributes#getTypes() with generic scenario
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-416 Extend tests for BeanAttributes#getTypes() with generic scenario Change By: Matus Abaffy Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/69 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1682) BeanManager lookup fails with WELD-001328 when calling class is not a bean
Title: Message Title Matus Abaffy commented on WELD-1682 Re: BeanManager lookup fails with WELD-001328 when calling class is not a bean Yes, I understand. I was just responding to your workaround: Changing the CdiUtil class to be non-final with @Dependent fixes the error, but now my class is a bean, even though it should not be used this way. from which I thought that you have a problem when the class is a bean. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1682) BeanManager lookup fails with WELD-001328 when calling class is not a bean
Title: Message Title Matus Abaffy commented on WELD-1682 Re: BeanManager lookup fails with WELD-001328 when calling class is not a bean If you have problems with the CdiUtil class being recognized as a bean, try to annotate it with @javax.enterprise.inject.Vetoed. It should solve the problem. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-418) InterceptorEnvironmentJNDISessionBeanTest is not portable
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-418 InterceptorEnvironmentJNDISessionBeanTest is not portable Change By: Matus Abaffy Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/68 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1599) Class WeldCreationalContext has the same simple name as the interface
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1599 Class WeldCreationalContext has the same simple name as the interface Change By: Matus Abaffy Summary: Class WeldCreationalContext have has the same simple name as the interface Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-416) Extend tests for BeanAttributes#getTypes() with generic scenario
Title: Message Title Matus Abaffy created an issue CDI TCK / CDITCK-416 Extend tests for BeanAttributes#getTypes() with generic scenario Issue Type: Task Affects Versions: 1.2.0.Final Assignee: Matus Abaffy Components: Tests Created: 15/May/14 8:45 AM Priority: Major Reporter: Matus Abaffy Security Level: Public (Everyone can see) The most important: Add tests where a bean class extends the raw type of a parameterized class. Add Comment
[weld-issues] [JBoss JIRA] (WELD-1677) BeanAttributes.getTypes() returns also canonical types
Title: Message Title
Matus Abaffy created an issue
Weld / WELD-1677
BeanAttributes.getTypes() returns also canonical types
Issue Type:
Bug
Affects Versions:
2.2.1.Final
Assignee:
Jozef Hartinger
Created:
15/May/14 8:39 AM
Priority:
Major
Reporter:
Matus Abaffy
When a bean class A extends the raw type of a parameterized class B, canonical types of B are added into types of A (in org.jboss.weld.util.reflection.HierarchyDiscovery#discoverTypes()). That causes problems in specialization validation as the getTypes() method of the specializing bean A returns even types it does not have.
Example:
class B implements Collection { ... }
class A extends B { ... }
Collection should not be a type of bean A.
[weld-issues] [JBoss JIRA] (WELD-1651) Specialization of generic beans throws inappropriate exception
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1651 Specialization of generic beans throws inappropriate exception Change By: Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/552 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1671) Revise EventTypeAssignabilityRules
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1671 Revise EventTypeAssignabilityRules Change By: Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/565 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding WELD-1671
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-414 Create tests regarding WELD-1671 Change By: Matus Abaffy Test bean assignability regarding parameterized type with type variable(s) with multiple bounds. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding WELD-1671
Title: Message Title Matus Abaffy updated an issue CDI TCK / CDITCK-414 Create tests regarding WELD-1671 Change By: Matus Abaffy Test bean assignability regarding parameterized type with multiple bounds. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1651) Specialization of generic beans throws inappropriate exception
Title: Message Title Matus Abaffy commented on WELD-1651 Re: Specialization of generic beans throws inappropriate exception The existence of the workaround when specializing bean's class extends the raw type of the generic superclass is a bug and should not work. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding WELD-1671
Title: Message Title Matus Abaffy created an issue CDI TCK / CDITCK-414 Create tests regarding WELD-1671 Issue Type: Task Affects Versions: 1.2.0.Final Assignee: Matus Abaffy Created: 07/May/14 10:54 AM Priority: Major Reporter: Matus Abaffy Security Level: Public (Everyone can see) Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6)
[weld-issues] [JBoss JIRA] (WELD-1671) Revise EventTypeAssignabilityRules
Title: Message Title Matus Abaffy created an issue Weld / WELD-1671 Revise EventTypeAssignabilityRules Issue Type: Bug Affects Versions: 2.2.0.SP2 Assignee: Matus Abaffy Created: 07/May/14 10:48 AM Priority: Major Reporter: Matus Abaffy In EventTypeAssignabilityRules, method isAssignableFrom(Type type1, Type[] types2) seems to be incorrect - it is called from isTypeInsideBounds() with expectation that type1 has to assignableFrom each Type from types2, not from at least one as is the case. Other such incorrect methods are: isAssignableFrom(Type type1, Set types2) isAssignableFrom(Type[] types1, Type type2) Add Comment
[weld-issues] [JBoss JIRA] (WELD-1666) SessionBeanInterceptor never sets EjbRequestContext properly
Title: Message Title Matus Abaffy updated an issue Weld / WELD-1666 SessionBeanInterceptor never sets EjbRequestContext properly Change By: Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/559 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1651) Specialization of generic beans throws inappropriate exception
Title: Message Title
Matus Abaffy updated an issue
Weld / WELD-1651
Specialization of generic beans throws inappropriate exception
Change By:
Matus Abaffy
Workaround Description:
In the subclass declaration, reference the superclass without type parameters after the 'extends' keyword. That will result to a warning which can be suppressed using @SuppressWarnings("rawtypes").Following the example from the description, the specializing class would look like this:{code}@Specializespublic class BeanCustom extends BeanDefault {}{code}This way, type parameters of the specialized bean's bean types will be exactly the same (also equal in the java sense) as the type parameters of the specializing bean's bean types which are implied from extending the specialized class.
Workaround:
Workaround Exists
Add Comment
This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-411) Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e)
Matus Abaffy
created CDITCK-411
Improve coverage of Assignability of raw and parameterized types, assertion 5.2.4. e)
Issue Type:
Task
Affects Versions:
1.2.0.CR1
Assignee:
Matus Abaffy
Created:
28/Apr/14 4:57 AM
Description:
Changing an IF statement in org.jboss.weld.resolution.BeanTypeAssignabilityRules#isAssignableFrom(ActualTypeHolder requiredType, Type otherType)
from
if (isTypeInsideBounds(requiredType, EMPTY_TYPES, typeVariable.getBounds())) {
to
if (isTypeInsideBounds(requiredType, typeVariable.getBounds(), EMPTY_TYPES)) {
does not cause any test failure.
Project:
CDI TCK
Priority:
Major
Reporter:
Matus Abaffy
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] (WELD-1645) Improve AfterBeanDiscovery input validation
Matus Abaffy updated WELD-1645 Improve AfterBeanDiscovery input validation Change By: Matus Abaffy (03/Apr/14 9:42 AM) Git Pull Request: https://github.com/weld/core/pull/530 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-1623) Cleanup of expired conversations should be synchronized
Matus Abaffy updated WELD-1623 Cleanup of expired conversations should be synchronized Change By: Matus Abaffy (31/Mar/14 8:30 AM) Git Pull Request: https://github.com/weld/core/pull/519 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-1628) BeansXmlHandler must not call interpolate() method if the value to interpoate is null
Matus Abaffy updated WELD-1628 BeansXmlHandler must not call interpolate() method if the value to interpoate is null Change By: Matus Abaffy (25/Mar/14 5:30 AM) Git Pull Request: https://github.com/weld/core/pull/509 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-399) Add tests for stereotypes as bean defining annotations
Matus Abaffy resolved CDITCK-399 as Done Add tests for stereotypes as bean defining annotations Change By: Matus Abaffy (24/Mar/14 6:05 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] (CDITCK-398) Add tests for @Interceptor and @Decorator as bean defining annotations
Matus Abaffy resolved CDITCK-398 as Done Add tests for @Interceptor and @Decorator as bean defining annotations Change By: Matus Abaffy (24/Mar/14 6:05 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] (CDITCK-400) Switch sections 10.2 and 10.3
Matus Abaffy updated CDITCK-400 Switch sections 10.2 and 10.3 Change By: Matus Abaffy (17/Mar/14 8:15 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/49 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-399) Add tests for stereotypes as bean defining annotations
Matus Abaffy updated CDITCK-399 Add tests for stereotypes as bean defining annotations Change By: Matus Abaffy (17/Mar/14 7:54 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/48 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-1620) Cannot declare multiple disposal methods for this producer method.
Matus Abaffy
commented on WELD-1620
Cannot declare multiple disposal methods for this producer method.
Explicitly annotate the disposed parameter as @Default. This should work: public void dispose(@Disposes @Default Something instance)
{ ... }
.
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-398) Add tests for @Interceptor and @Decorator as bean defining annotations
Matus Abaffy updated CDITCK-398 Add tests for @Interceptor and @Decorator as bean defining annotations Change By: Matus Abaffy (13/Mar/14 4:23 PM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/48 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-353) Interceptors spec - create tests for section 2.2 Interceptor Life Cycle
Matus Abaffy updated CDITCK-353 Interceptors spec - create tests for section 2.2 Interceptor Life Cycle Change By: Matus Abaffy (20/Feb/14 11:06 AM) Fix Version/s: 1.2.0.Beta1 Fix Version/s: 1.2.0.Beta2 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-353) Interceptors spec - create tests for section 2.2 Interceptor Life Cycle
Matus Abaffy resolved CDITCK-353 as Done Interceptors spec - create tests for section 2.2 Interceptor Life Cycle Marking as Resolved as the only remaining subtask was resolved. When the interceptors_spec clarification requests are resolved, we should look whether the current tests are compliant with the changes. New assertions may arise as well. For that, new issue should be created if necessary. Change By: Matus Abaffy (20/Feb/14 11:04 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] (CDITCK-382) Interceptors spec - create tests regarding transaction context
Matus Abaffy updated CDITCK-382 Interceptors spec - create tests regarding transaction context Change By: Matus Abaffy (18/Feb/14 10:21 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/46 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-1596) Latest Weld 2.x gives AccessControlException on Google App Engine
Matus Abaffy updated WELD-1596 Latest Weld 2.x gives AccessControlException on Google App Engine Change By: Matus Abaffy (12/Feb/14 9:00 AM) Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/476 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-1596) Latest Weld 2.x gives AccessControlException on Google App Engine
Matus Abaffy commented on WELD-1596 Latest Weld 2.x gives AccessControlException on Google App Engine Yes, I confirm that I got the aforementioned AccessControlException after deploying the same application on the appspot. 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-1596) Latest Weld 2.x gives AccessControlException on Google App Engine
Matus Abaffy edited a comment on WELD-1596 Latest Weld 2.x gives AccessControlException on Google App Engine Hi, I tried deploying a simple jsf application (on my local appengine-java-sdk-1.8.9 distribution using Weld 2.2.0.Alpha1 on Linux) and everything worked fine - no exception. 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-1596) Latest Weld 2.x gives AccessControlException on Google App Engine
Matus Abaffy commented on WELD-1596 Latest Weld 2.x gives AccessControlException on Google App Engine Hi, I tried deploying a simple jsf application (on my local appengine-java-sdk-1.8.9 distribution using Weld 2.2.0.Alpha1 on Linux) and everything worked fine - no exception. When does this exception occur? Could you provide some reproducer? I don't want to underestimate you but could you take a look at http://stackoverflow.com/questions/16229323/java-security-accesscontrolexception-access-denied-java-lang-runtimepermission and tell if it doesn't help you? Especially "If you are planning to deploy your project in GAE... You cannot use local resources like your own database, file-system, sockets, etc." Just to be sure that this really is a Weld bug. 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-390) Extend InterceptorBindingInheritanceTest
Matus Abaffy resolved CDITCK-390 as Done Extend InterceptorBindingInheritanceTest Change By: Matus Abaffy (31/Jan/14 8:44 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] (CDITCK-388) Create tests for remote EJB observer methods
Matus Abaffy resolved CDITCK-388 as Done Create tests for remote EJB observer methods Change By: Matus Abaffy (30/Jan/14 11:01 AM) Status: Open Resolved Fix Version/s: 1.2.0.Alpha1 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] (CDITCK-388) Create tests for remote EJB observer methods
Matus Abaffy updated CDITCK-388 Create tests for remote EJB observer methods Change By: Matus Abaffy (30/Jan/14 11:01 AM) Affects Version/s: 1.2.0.Alpha1 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-388) Create tests for remote EJB observer methods
Matus Abaffy commented on CDITCK-388 Create tests for remote EJB observer methods Also check, whether there are tests for local, no-interface and static observers too. 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-393) QualifierEquivalenceTest makes wrong assumption about Bean#getQualifiers()
Matus Abaffy closed CDITCK-393 as Duplicate Issue QualifierEquivalenceTest makes wrong assumption about Bean#getQualifiers() Change By: Matus Abaffy (30/Jan/14 3:08 AM) Status: Resolved Closed 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-392) QualifierEquivalenceTest makes wrong assumption about Bean#getQualifiers()
Matus Abaffy closed CDITCK-392 as Duplicate Issue QualifierEquivalenceTest makes wrong assumption about Bean#getQualifiers() Change By: Matus Abaffy (30/Jan/14 3:08 AM) Status: Resolved Closed 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-388) Create tests for remote EJB observer methods
Matus Abaffy created CDITCK-388 Create tests for remote EJB observer methods Issue Type: Task Affects Versions: 1.2.0.Alpha1 Assignee: Matus Abaffy Created: 28/Jan/14 11:08 AM Description: Possible inspiration from WELD-364 pull request. Project: CDI TCK Priority: Major Reporter: Matus Abaffy 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-382) Interceptors spec - create tests regarding transaction context
Matus Abaffy assigned CDITCK-382 to Matus Abaffy Interceptors spec - create tests regarding transaction context Change By: Matus Abaffy (24/Jan/14 11:35 AM) Assignee: Matus Abaffy 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-345) Add tests for EE component setter injection
Matus Abaffy updated CDITCK-345 Add tests for EE component setter injection Change By: Matus Abaffy (21/Jan/14 6:22 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/45 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-345) Add tests for EE component setter injection
Matus Abaffy stopped work on CDITCK-345 Add tests for EE component setter injection Change By: Matus Abaffy (21/Jan/14 6:23 AM) Status: Coding In Progress Open 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-345) Add tests for EE component setter injection
Matus Abaffy started work on CDITCK-345 Add tests for EE component setter injection Change By: Matus Abaffy (21/Jan/14 6:22 AM) Status: Open Coding In Progress 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-1583) Confusing error message when an interceptor/decorator has a non-passivating dependency
Matus Abaffy updated WELD-1583 Confusing error message when an interceptor/decorator has a non-passivating dependency Change By: Matus Abaffy (20/Jan/14 6:10 AM) Status: Pull Request Sent 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-1586) Ambiguous dependency not detected for (two) session beans with the same name
Matus Abaffy updated WELD-1586 Ambiguous dependency not detected for (two) session beans with the same name Change By: Matus Abaffy (16/Jan/14 8:07 AM) Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/456 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-1586) Ambiguous dependency not detected for (two) session beans with the same name
Matus Abaffy
created WELD-1586
Ambiguous dependency not detected for (two) session beans with the same name
Issue Type:
Bug
Affects Versions:
2.1.2.Final
Assignee:
Matus Abaffy
Components:
Class Beans (Managed and Session)
Created:
16/Jan/14 8:00 AM
Description:
Two session beans:
same name
implementing the same local interface (Animal) and declaring no other views
deployed in two different modules, one module (A) is visible to the other (B).
When trying to inject Animal in the module B, once I get an instance of the first bean, next time an instance of the second one. The correct behavior would be DeploymentException due to ambiguous dependency.
interface Animal {}
@Stateful(name = "Animal")
public class Cat implements Animal {}
@Stateful(name = "Animal")
public class Dog implements Animal {}
public class Bar {
@Inject
private Animal animal;
}
Deployment structure:
EAR
ejb.jar: Animal, Dog
test.war: Bar, Cat
Project:
Weld
Priority:
Major
Reporter:
Matus Abaffy
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-384) Create tests for observer method invocation context
Matus Abaffy assigned CDITCK-384 to Matus Abaffy Create tests for observer method invocation context Change By: Matus Abaffy (15/Jan/14 3:58 AM) Assignee: Martin Kouba Matus Abaffy 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-1583) Confusing error message when an interceptor/decorator has a non-passivating dependency
Matus Abaffy updated WELD-1583 Confusing error message when an interceptor/decorator has a non-passivating dependency Change By: Matus Abaffy (13/Jan/14 8:46 AM) Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/452 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-354) Interceptors spec - improve coverage of section 2.7 Timeout Method Interceptors
Matus Abaffy resolved CDITCK-354 as Done Interceptors spec - improve coverage of section 2.7 Timeout Method Interceptors Change By: Matus Abaffy (13/Jan/14 5:55 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-1562) Multiple specialization doesn't work
Matus Abaffy commented on WELD-1562 Multiple specialization doesn't work Thanks for pointing out. We'll add this test to 2.2 branch. 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-1576) @EJB injection in interceptor class and in target class result in injection of instances of two different classes
Matus Abaffy
updated WELD-1576
@EJB injection in interceptor class and in target class result in injection of instances of two different classes
Change By:
Matus Abaffy
(20/Dec/13 12:23 PM)
Description:
Interceptors spec, 2.2.1 - Interceptor Environment:bq. Interceptor class shares the enterprise naming context of its associated target class. (1)Assume the following scenario:Ear: test-ejb.jar, test1.war, test2.war test-ejb.jar: Animal, BarBinding test1.war: BarInterceptor, Dog test2.war: Bar, CatShort description of the classes:{code}@Stateful public class Dog implements Animal {...}{code}{code}@Stateful public class Cat implements Animal {...}{code}{code}@BarBinding @Statelesspublic class Bar {@EJBAnimal animal;}{code}{code}@BarBinding @Priority(1000) @Interceptorpublic class BarInterceptor {@EJBAnimal animal;}{code}Bar gets injected an instance of Cat, whereas BarInterceptor gets injected an instance of Dog, which IMHO contradicts (1).Test case at: https://github.com/
bafco
cdi-spec
/cdi-tck/
tree
pull
/
CDITCK-369
38
(
org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.jndi.ejb.InterceptorEnvironmentEjbTest
InterceptorEnvironmentJNDITest, InterceptorEnvironmentJNDISessionBeanTest
)
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-369) Interceptors spec - create tests for section 2.2.1 Interceptor Environment
Matus Abaffy updated CDITCK-369 Interceptors spec - create tests for section 2.2.1 Interceptor Environment Change By: Matus Abaffy (20/Dec/13 12:05 PM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/38 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-1576) @EJB injection in interceptor class and in target class result in injection of instances of two different classes
Matus Abaffy
updated WELD-1576
@EJB injection in interceptor class and in target class result in injection of instances of two different classes
Change By:
Matus Abaffy
(20/Dec/13 8:23 AM)
Description:
Interceptors spec, 2.2.1 - Interceptor Environment:bq. Interceptor class shares the enterprise naming context of its associated target class. (1)Assume the following scenario:Ear: test-ejb.jar, test1.war, test2.war test-ejb.jar: Animal, BarBinding test1.war: BarInterceptor, Dog test2.war: Bar, CatShort description of the classes:{code}@Stateful public class Dog implements Animal {...}{code}{code}@Stateful public class Cat implements Animal {...}{code}{code}@BarBinding @Statelesspublic class Bar {@EJBAnimal animal;}{code}{code}@BarBinding @Priority(1000) @Interceptorpublic class BarInterceptor {@EJBAnimal animal;}{code}Bar gets injected an instance of Cat, whereas BarInterceptor gets injected an instance of Dog, which IMHO contradicts (1).Test case at: https://github.com/bafco/cdi-tck/tree/
beanAccessibility
CDITCK-369
(org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.jndi.ejb.InterceptorEnvironmentEjbTest)
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-1576) @EJB injection in interceptor class and in target class result in injection of instances of two different classes
Matus Abaffy
created WELD-1576
@EJB injection in interceptor class and in target class result in injection of instances of two different classes
Issue Type:
Bug
Affects Versions:
2.1.1.Final
Assignee:
Jozef Hartinger
Components:
Interceptors and Decorators, WildFly integration
Created:
20/Dec/13 8:15 AM
Description:
Interceptors spec, 2.2.1 - Interceptor Environment:
Interceptor class shares the enterprise naming context of its associated target class. (1)
Assume the following scenario:
Ear: test-ejb.jar, test1.war, test2.war
test-ejb.jar: Animal, BarBinding
test1.war: BarInterceptor, Dog
test2.war: Bar, Cat
Short description of the classes:
@Stateful public class Dog implements Animal {...}
@Stateful public class Cat implements Animal {...}
@BarBinding @Stateless
public class Bar {
@EJB
Animal animal;
}
@BarBinding @Priority(1000) @Interceptor
public class BarInterceptor {
@EJB
Animal animal;
}
Bar gets injected an instance of Cat, whereas BarInterceptor gets injected an instance of Dog, which IMHO contradicts (1).
Test case at: https://github.com/bafco/cdi-tck/tree/beanAccessibility
(org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.jndi.ejb.InterceptorEnvironmentEjbTest)
Project:
Weld
Priority:
Major
Reporter:
Matus Abaffy
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-1572) Validating interceptors of a bean which declares a passivating scope uses the bean's bean manager instead of interceptor's BM
Matus Abaffy created WELD-1572 Validating interceptors of a bean which declares a passivating scope uses the bean's bean manager instead of interceptor's BM Issue Type: Bug Affects Versions: 2.1.1.Final Assignee: Matus Abaffy Components: Interceptors and Decorators Created: 19/Dec/13 5:33 AM Description: When validating whether a bean is passivation capable, org.jboss.weld.bootstrap.Validator uses the bean's bean manager for validating injection points of its interceptors, which can result in incorrect exception due to ambiguous dependency: org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318: Cannot resolve an ambiguous dependency between: - Managed Bean [class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Dog] with qualifiers [@Any @Default], - Managed Bean [class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Cat] with qualifiers [@Any @Default] at org.jboss.weld.manager.BeanManagerImpl.resolve(BeanManagerImpl.java:1181) at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:221) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:504) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_17] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_17] ... 3 more -> Class org.jboss.cdi.tck.tests.lookup.modules.interceptors.Cat is not (required to be) accessible to the module containing the interceptor class with injection point causing this exception. Test case: https://github.com/bafco/cdi-tck/tree/beanAccessibility Project: Weld Priority: Major Reporter: Matus Abaffy 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-377) Interceptors spec - duplicate existing interceptor tests to test session beans too
Matus Abaffy resolved CDITCK-377 as Done Interceptors spec - duplicate existing interceptor tests to test session beans too Change By: Matus Abaffy (18/Dec/13 6:42 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] (CDITCK-376) Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors
Matus Abaffy resolved CDITCK-376 as Done Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors Change By: Matus Abaffy (18/Dec/13 6:41 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] (CDITCK-354) Interceptors spec - improve coverage of section 2.7 Timeout Method Interceptors
Matus Abaffy updated CDITCK-354 Interceptors spec - improve coverage of section 2.7 Timeout Method Interceptors Change By: Matus Abaffy (16/Dec/13 5:22 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/37 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-382) Interceptors spec - create tests regarding transaction context
Matus Abaffy updated CDITCK-382 Interceptors spec - create tests regarding transaction context Change By: Matus Abaffy (13/Dec/13 5:47 AM) Assignee: Martin Kouba 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-382) Interceptors spec - create tests regarding transaction context
Matus Abaffy created CDITCK-382 Interceptors spec - create tests regarding transaction context Issue Type: Task Assignee: Martin Kouba Created: 13/Dec/13 5:46 AM Description: Such uncovered assertions are under sections 2.5, 2.6, 2.7. Fix Versions: 1.2.0.Alpha1 Project: CDI TCK Priority: Major Reporter: Matus Abaffy 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-376) Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors
Matus Abaffy updated CDITCK-376 Interceptors spec - improve tests for setcion Section 2.5 - Business Method Interceptors Change By: Matus Abaffy (13/Dec/13 5:40 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/35 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-1562) Multiple specialization doesn't work
Matus Abaffy updated WELD-1562 Multiple specialization doesn't work Change By: Matus Abaffy (03/Dec/13 11:57 AM) Assignee: Jozef Hartinger Matus Abaffy Git Pull Request: https://github.com/weld/core/pull/430 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-1562) Multiple specialization doesn't work
Matus Abaffy
commented on WELD-1562
Multiple specialization doesn't work
Current behavior does not conform to the spec (namely 4.3.1. Direct and indirect specialization) as the class BeanC DOES NOT INHERIT the BeanA's NAME, only BeanB does. Therefore BeanC is not included in the set of beans returned by beanManager.getBeans("beanA").
We did not reproduce the problem because the tests used
Set> javax.enterprise.inject.spi.BeanManager.getBeans(Type beanType, Annotation... qualifiers);
instead of
Set> javax.enterprise.inject.spi.BeanManager.getBeans(String name);
.
A simple workaround is to annotate the BeanC class with @Named("beanA").
So it has nothing to do with WELD-1561.
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-1562) Multiple specialization doesn't work
Matus Abaffy
updated WELD-1562
Multiple specialization doesn't work
Change By:
Matus Abaffy
(02/Dec/13 2:36 PM)
Description:
{code}
@Named
public class BeanA {...}{code}{code}@Specializespublic class BeanB extends BeanA {...}{code}{code}@Specializespublic class BeanC extends BeanB {public String getPropC() { return "PropC from BeanC here!"; }}{code}
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-1562) Multiple specialization doesn't work
Matus Abaffy commented on WELD-1562 Multiple specialization doesn't work Yeah, the specialization works fine. Even when I tested this scenario in servlet (jetty), the problem didn't occur. Honestly, I'm not 100% sure about the cause of the aforementioned exception. 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-1562) Multiple specialization doesn't work
Matus Abaffy commented on WELD-1562 Multiple specialization doesn't work Actually, the problem is caused by incompatibility with new Jetty, see https://issues.jboss.org/browse/WELD-1561 SEVERE: Unable to create JettyWeldInjector. CDI injection will not be available in Servlets, Filters or Listeners java.lang.IllegalArgumentException: Cannot load class for org.jboss.weld.environment.jetty.WeldDecorator at org.jboss.weld.environment.servlet.util.Reflections.classForName(Reflections.java:58) at org.jboss.weld.environment.jetty.JettyPost72Container.initialize(JettyPost72Container.java:61) at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:162) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:787) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:434) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:779) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:284) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1322) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:731) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:490) at org.eclipse.jetty.maven.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:280) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.Server.start(Server.java:342) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:90) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:58) at org.eclipse.jetty.server.Server.doStart(Server.java:290) at org.eclipse.jetty.maven.plugin.JettyServer.doStart(JettyServer.java:68) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69) at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:563) at org.eclipse.jetty.maven.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:359) at org.eclipse.jetty.maven.plugin.JettyRunMojo.execute(JettyRunMojo.java:167) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214) at org.apache.maven.cli.MavenCli.main(MavenCli.java:158) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at or
[weld-issues] [JBoss JIRA] (WELD-1562) Multiple specialization doesn't work
Matus Abaffy commented on WELD-1562 Multiple specialization doesn't work org.jboss.weld.tests.specialization.ExtSpecializationTest already covers a scenario with indirect (transitive) specialization and passes. I added org.jboss.weld.tests.specialization.MultipleSpecializationTest (see https://github.com/bafco/core/commits/WELD-1562) that tests also the invocation of methods of the specializing class and it passes too. However, with Jetty, a proxy for BeanB is created instead of BeanC and the following error occurs: javax.el.ELException: /views/index.xhtml: The class 'test.BeanB$Proxy$_$$_WeldClientProxy' does not have the property 'propC'. at com.sun.faces.facelets.compiler.TextInstruction.write(TextInstruction.java:88) at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:207) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1822) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.render(DeltaSpikeLifecycleWrapper.java:97) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:698) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:505) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:582) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1096) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:432) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1030) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:261) at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:101) at org.eclipse.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:546) at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:698) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:505) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:138) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:564) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:213) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1096) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:432) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:175) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1030) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:136) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:201) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:445) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:268) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.run(AbstractConnection.java:358) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:601) at org.eclipse.jetty.util.thread.Queue
[weld-issues] [JBoss JIRA] (WELD-1562) Multiple specialization doesn't work
Matus Abaffy
updated WELD-1562
Multiple specialization doesn't work
Change By:
Matus Abaffy
(29/Nov/13 3:29 PM)
Description:
e
{code}public class BeanA {
.
g
.
.}
{code}
BeanA
{code}
@
Specialized
Specializespublic class
BeanB extends BeanA
{...}
{code}{code}
@
Specialized
Specializespublic class
BeanC extends BeanB
{public String getPropC() { return "PropC from BeanC here!"; }}{code}
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-1558) Proxy naming conflict when using static nested classes with the same name and package.
Matus Abaffy updated WELD-1558 Proxy naming conflict when using static nested classes with the same name and package. Change By: Matus Abaffy (27/Nov/13 7:35 AM) Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/421 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-1560) CustomCDIProviderTest based on incorrect assumption
Matus Abaffy updated WELD-1560 CustomCDIProviderTest based on incorrect assumption Change By: Matus Abaffy (27/Nov/13 7:35 AM) Status: Open Pull Request Sent Git Pull Request: https://github.com/weld/core/pull/422 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-1560) CustomCDIProviderTest based on incorrect assumption
Matus Abaffy created WELD-1560 CustomCDIProviderTest based on incorrect assumption Issue Type: Bug Affects Versions: 2.1.0.Final Assignee: Matus Abaffy Components: Java SE Support, Servlet Container Support Created: 25/Nov/13 10:08 AM Description: Tests which need to be fixed: org.jboss.weld.environment.servlet.test.provider.CustomCDIProviderTestBase org.jboss.weld.environment.se.test.provider.custom.CustomCDIProviderTest For description, see https://issues.jboss.org/browse/CDITCK-375 Fix Versions: 2.1.1.Final Project: Weld Priority: Major Reporter: Matus Abaffy 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-1558) Proxy naming conflict when using static nested classes with the same name and package.
Matus Abaffy edited a comment on WELD-1558 Proxy naming conflict when using static nested classes with the same name and package. Scenario: Classes Bar and Baz, both with normal scoped inner static class Foo. @Inject Bar.Foo barFoo; @Inject Baz.Foo bazFoo results in the following error: java.lang.IllegalArgumentException: Can not set org.jboss.weld.tests.proxy.weld1558.Bar$Foo field org.jboss.weld.tests.proxy.weld1558.StaticNestedClassesProxyTest.barFoo to org.jboss.weld.tests.proxy.weld1558.Foo$Proxy$_$$_WeldClientProxy at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81) at java.lang.reflect.Field.set(Field.java:680) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) ... 81 more When injecting only a single Foo (e.g. Bar.Foo barFoo), its FQCN is org.jboss.weld.tests.proxy.weld1558.Foo$Proxy$_$$_WeldClientProxy, i.e. the same for both Foos. 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-1558) Proxy naming conflict when using static nested classes with the same name and package.
Matus Abaffy commented on WELD-1558 Proxy naming conflict when using static nested classes with the same name and package. Scenario: Classes Bar and Baz, both with normal scoped inner static class Foo. @Inject Bar.Foo barFoo; @Inject Baz.Foo bazFoo results in the following error: java.lang.IllegalArgumentException: Can not set org.jboss.weld.tests.proxy.weld1558.Bar$Foo field org.jboss.weld.tests.proxy.weld1558.StaticNestedClassesProxyTest.barFoo to org.jboss.weld.tests.proxy.weld1558.Foo$Proxy$_$$_WeldClientProxy at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:168) at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81) at java.lang.reflect.Field.set(Field.java:680) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:94) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:145) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:125) ... 81 more 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-1557) Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing
Matus Abaffy
updated WELD-1557
Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing
Change By:
Matus Abaffy
(22/Nov/13 12:10 PM)
Description:
Consider the following scenario:Session bean Foo is intercepted by interceptor I1, bound using interceptor binding. I1 extends I2, I2 extends I3. Classes I1, I2, I3 declare around-invoke methods (with different names). However, only I3's around-invoke method is invoked.(Generally, only the around-invoke method of the topmost superclass of the interceptor class which declares an around-invoke method is invoked. If no interceptor's superclass declares any around-invoke method, the interceptor's around-invoke method is invoked correctly.)The same is true for around-timeout methods
and lifecycle callback methods
.Such testcase is available at https://github.com/bafco/cdi-tck/commits/CDITCK-376 (SessionBeanAroundInvokeInterceptorTest){code}@Stateless @Bindingclass Foo { void ping() {} }@Interceptor @Binding @Priority(1001)class I1 extends I2 {@AroundInvokepublic Object intercept2(InvocationContext ctx) throws Exception {return ctx.proceed();}}class I2 extends I3 {@AroundInvokepublic Object intercept1(InvocationContext ctx) throws Exception {return ctx.proceed();}}class I3 {@AroundInvokepublic Object intercept0(InvocationContext ctx) throws Exception {return ctx.proceed();}}{code}The aforementioned scenario works fine with CDI managed beans and with interceptors bound using @Interceptors annotation.
With lifecycle callback methods it is more complicated. For example, AroundConstruct scenario works for @Stateless, but does not work for @Stateful.
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-377) Interceptors spec - duplicate existing interceptor tests to test session beans too
Matus Abaffy created CDITCK-377 Interceptors spec - duplicate existing interceptor tests to test session beans too Issue Type: Task Affects Versions: 1.1.2.Final Assignee: Matus Abaffy Created: 20/Nov/13 5:09 AM Description: There are no complex interceptor tests with session beans.However, intercepting session beans does not work the same way as intercepting CDI managed beans. For example, see WELD-1557 Fix Versions: 1.2.0.Alpha1 Project: CDI TCK Priority: Major Reporter: Matus Abaffy 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] (WELD-1557) Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing
Matus Abaffy updated WELD-1557 Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing Change By: Matus Abaffy (19/Nov/13 2:07 PM) Affects Version/s: 2.1.0.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-1557) Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing
Matus Abaffy updated WELD-1557 Interceptor methods not invoked correctly on session bean interceptors bound using bindings in case of subclassing Change By: Matus Abaffy (19/Nov/13 2:07 PM) Issue Type: Task Bug 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
