September 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-793) Make bootstrap more granular

by Pete Muir (JIRA)

Make bootstrap more granular ---------------------------- Key: WELD-793 URL: https://issues.jboss.org/browse/WELD-793 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.0.CR1 Reporter: Pete Muir Priority: Blocker Fix For: 1.2.0.Beta1 Currently the bootstrap is fairly coarse grained, not allowing the container to "skip" parts of bootstrap if it can provide the information externally. The primary goal here is to allow the container to skip the the bootstrap up until after all ProcessAnnotatedType events have been sent, and the modified class metadata has been built. My proposal for this is to introduce a new method to bootstrap that passes in a map of BDA->AnnotatedType that Weld can use to boot. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-921) Incorrect handling of business interfaces for EJBs (where defining class of business method is not the Business interface of the EJBs)

by Sivakumar Thyagarajan (JIRA)

Incorrect handling of business interfaces for EJBs (where defining class of business method is not the Business interface of the EJBs) --------------------------------------------------------------------------------------------------------------------------------------- Key: WELD-921 URL: https://issues.jboss.org/browse/WELD-921 Project: Weld Issue Type: Bug Components: Weld SPI Affects Versions: 1.1.1.Final, 1.1.0.Final Reporter: Sivakumar Thyagarajan Fix For: 1.1.2.Final This is based on the scenario described in http://java.net/jira/browse/GLASSFISH-16186 - @Named @Stateless TimeProviderImpl extends SimpleTimeProvider implements LocalTimeProvider. - SimpleTimeProvider implements TimeProvider (the latter defining some methods, the former implementing them. No annotations.) - LocalTimeProvider is @Local and also extends TimeProvider and does nothing more. So the Local Business interface is LocalTimeProvider. The following injection is performed on a SessionScoped Bean @Inject private LocalTimeProvider timeProvider1; The Weld bean proxy for the SessionBean Object reference being injected(timeProvider1) tries to get [1] the BusinessObject when a method is invoked on it. Weld seems to use [2] the declaring class of the method being invoked to determine the business interface. Though the business interface of the Bean is set to com.dummy.time.LocalTimeProvider, the class that declares the method being invoked ("getThisMonth()") is com.dummy.time.TimeProvider. Therefore, the Weld implementation calls SessionObjectReferenceImpl.getBusinessObject("com.dummy.time.TimeProvider"), which fails, as TimeProvider is not a Business interface. As per [3], the businessInterfaceType must be a type of the business interface of the bean. Is Weld incorrect in mapping the method to its declaring interface. Weld must instead use the injected type as the business interface, while trying to get the business object. [1] https://github.com/weld/core/blob/76c31d311cf1ff449eb2d5c80943b913651bed9... [2]https://github.com/weld/core/blob/76c31d311cf1ff449eb2d5c80943b913651be... [3] https://github.com/weld/api/blob/master/weld-spi/src/main/java/org/jboss/... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

7
12
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

11 years, 7 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

11 years, 7 months

3
4
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

11 years, 8 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

11 years, 8 months

4
7
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

11 years, 8 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

11 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (WELD-975) Programmatic lookup with @New qualifier not working

by Martin Kouba (JIRA)

Programmatic lookup with @New qualifier not working --------------------------------------------------- Key: WELD-975 URL: https://issues.jboss.org/browse/WELD-975 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Environment: JBoss AS7 TestNG Arquillian CR5 Reporter: Martin Kouba According to spec: "...the @New qualifier may be used, allowing the application to obtain a @New qualified bean, as defined in Section 3.12, @New qualified beans" (CDI 1.0; chapter 5.6. Programmatic lookup). However using programmatic lookup with @New qualifier like: {code} @Inject @New Instance<Foo> foo; {code} results in: {code} org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [class org.jboss.cditck.arquillian.instance.Foo]; Bindings: [@javax.enterprise.inject.New(value=org.jboss.cditck.arquillian.instance.Foo.class)] {code} after trying to obtain reference via get() method. Following code works ok: {code} @Inject @New Foo foo; {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
10
0 / 0

[JBoss JIRA] Created: (WELD-458) Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error

by Ondrej Skutka (JIRA)

Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error ------------------------------------------------------------------------------------------------------------- Key: WELD-458 URL: https://jira.jboss.org/jira/browse/WELD-458 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: An interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as @Target(TYPE). If an interceptor for lifecycle callbacks declares an interceptor binding type that is defined @Target({TYPE, METHOD}), the con- tainer automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.interceptorForLifecycleTargetMethod.InterceptorForLifecycleTargetMethodTest In the TCK trunk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

6
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues September 2011