February 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-995) The built-in InjectionTarget implementation should use getInjectionPoints()

by Jozef Hartinger (Created) (JIRA)

The built-in InjectionTarget implementation should use getInjectionPoints() --------------------------------------------------------------------------- Key: WELD-995 URL: https://issues.jboss.org/browse/WELD-995 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1 See CDI-178 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
7
0 / 0

[JBoss JIRA] Created: (WELD-963) Change Singleton to use a Map of ids -> singletons

by Pete Muir (JIRA)

Change Singleton to use a Map of ids -> singletons -------------------------------------------------- Key: WELD-963 URL: https://issues.jboss.org/browse/WELD-963 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.2.Final Reporter: Pete Muir Fix For: 1.2.0.Beta1 This will allow for a more flexible approach to locating the singleton. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-962) Attach bda id and deployment id to the serialized proxy and use it on deserialization to locate correct singleton

by Pete Muir (JIRA)

Attach bda id and deployment id to the serialized proxy and use it on deserialization to locate correct singleton ----------------------------------------------------------------------------------------------------------------- Key: WELD-962 URL: https://issues.jboss.org/browse/WELD-962 Project: Weld Issue Type: Feature Request Components: Proxies Affects Versions: 1.1.2.Final Reporter: Pete Muir Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
4
0 / 0

[JBoss JIRA] (WELD-1038) Invocations of message listener methods of message-driven beans are not intercepted

by Martin Kouba (Created) (JIRA)

Invocations of message listener methods of message-driven beans are not intercepted ----------------------------------------------------------------------------------- Key: WELD-1038 URL: https://issues.jboss.org/browse/WELD-1038 Project: Weld Issue Type: Bug Reporter: Martin Kouba See chapters "7.2. Container invocations and interception" and "9. Interceptor bindings". TCK 1.1 test: *org.jboss.jsr299.tck.tests.interceptors.definition.enterprise.jms.MessageDrivenBeanInterceptorInvocationTest.testMessageDrivenBeanMethodIntercepted()* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (WELD-800) Add an initializationComplete() method to BeanManagerImpl

by Pete Muir (JIRA)

Add an initializationComplete() method to BeanManagerImpl --------------------------------------------------------- Key: WELD-800 URL: https://issues.jboss.org/browse/WELD-800 Project: Weld Issue Type: Feature Request Reporter: Pete Muir Fix For: 1.2.0.Beta1 BeanManagerImpl is mutable as we need to create the object early in bootstrap and then populate it with beans etc. Currently we don't make it immutable after bootstrap, but this would be good defensive programming, and also allow us to perhaps perform some optimizations on the data structures as we know they are then immutable. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
7
0 / 0

[JBoss JIRA] Created: (WELD-918) interceptor binding for java interfaces/methods

by Manuel Hartl (JIRA)

interceptor binding for java interfaces/methods ----------------------------------------------- Key: WELD-918 URL: https://issues.jboss.org/browse/WELD-918 Project: Weld Issue Type: Feature Request Components: Weld SPI Affects Versions: 1.1.0.Final Environment: tomcat6 Reporter: Manuel Hartl Priority: Minor - i created an interceptor and marked an java interface class with its binding (or a method of the interface) - interception does not work on methods of beans, that implement this interface. should this work? (interceptor binding to java interfaces?) if yes: it's a bug :) if no: please update weld documentation actually, i would like to use in interfaces -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
7
0 / 0

[JBoss JIRA] (WELD-1053) Event observers not fired when event object is of generic type

by Anton Lisovenko (JIRA)

Anton Lisovenko created WELD-1053: ------------------------------------- Summary: Event observers not fired when event object is of generic type Key: WELD-1053 URL: https://issues.jboss.org/browse/WELD-1053 Project: Weld Issue Type: Bug Components: Events Affects Versions: 1.1.0.Final Environment: Glassfish 3.1 Reporter: Anton Lisovenko CDI events are not fired when event object is not the compile-defined object, but the generic type. In this case the real object is defined in runtime and this is ok. But the event is not fired. Classes example and detailed description is available here (will not paste here so that not to make the description enormous): http://stackoverflow.com/questions/8962446/cdi-events-and-generics In addition to classes defined there will paste the entity classes: public interface Persistable extends Serializable { Long getId(); //... } and Polis class: @Entity public class Polis implements Persistable { //... fields and setters/getters here } Hope this will be enough -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
10
0 / 0

[JBoss JIRA] Created: (WELD-903) Shaded Weld SE artifact includes slf4j implementation

by Christian Bauer (JIRA)

Shaded Weld SE artifact includes slf4j implementation ----------------------------------------------------- Key: WELD-903 URL: https://issues.jboss.org/browse/WELD-903 Project: Weld Issue Type: Bug Components: Java SE Support Affects Versions: 1.1.1.Final Reporter: Christian Bauer Previously fixed but probably slipped through again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-930) Producer is made an alternative if the declaring bean class is an alternative

by Alexey Kazakov (JIRA)

Producer is made an alternative if the declaring bean class is an alternative ----------------------------------------------------------------------------- Key: WELD-930 URL: https://issues.jboss.org/browse/WELD-930 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.1.0.Final Reporter: Alexey Kazakov I'm looking at examples from https://github.com/pmuir/jboss-as-developer-guide/tree/master/quickstarts There is org.jboss.as.quickstarts.login.EJBUserManager: {code:title=org.jboss.as.quickstarts.login.EJBUserManager|borderStyle=solid} ... @Named("userManager") @RequestScoped @Alternative @Stateful public class EJBUserManager implements UserManager { ... @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } {code} And there is also another bean org.jboss.as.quickstarts.login.ManagedBeanUserManager: {code:title=org.jboss.as.quickstarts.login.ManagedBeanUserManager|borderStyle=solid} ... @Named("userManager") @RequestScoped public class ManagedBeanUserManager implements UserManager { @SuppressWarnings("unchecked") @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } {code} This code works in Weld even if EJBUserManager.getUsers() is not annotated @Alternative. But regarding the spec such a method has an ambiguous EL name "users": {quote} 5.3.1. Ambiguous EL names An ambiguous EL name exists in an EL expression when an EL name resolves to multiple beans. When an ambiguous EL name exists, the container attempts to resolve the ambiguity. If any of the beans are alternatives, the container eliminates all beans that are not alternatives, *except for producer methods and fields of beans that are alternatives*. If there is exactly one bean remaining, the container will select this bean, and the ambiguous EL name is called resolvable. {quote} There is a comment from Pete Muir: {quote} This looks to me like a bug in Weld (one that crept in from a pre-final spec revision) - that it checks if the declaring bean class is an alternative, and if it is, makes the producer an alternative. Can you file a WELD issue for this? I'll update the quickstart to explicitly make the producer an alternative. Pete {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
8
0 / 0

[JBoss JIRA] (WELD-1052) Unproxyable bean type check too strict

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1052: ------------------------------------- Summary: Unproxyable bean type check too strict Key: WELD-1052 URL: https://issues.jboss.org/browse/WELD-1052 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha2 According to the specification, a deployment that contains the following bean: {code:JAVA} public interface FooInterface { } @ApplicationScoped public final class Foo implements FooInterface { } {code} is valid as long as there is no injection point injecting Foo directly. The following injection point is valid: {code:JAVA} @Inject private FooInterface foo; {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues February 2012