July 2012 - weld-issues - Jboss List Archives

[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] (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

11 years, 8 months

7
10
0 / 0

[JBoss JIRA] (WELD-1161) beans.xml specified twice validation should happen before metadata map creation

by Mathieu Lachance (JIRA)

11 years, 8 months

3
4
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] (WELD-1153) Interceptor Performance Improvements

by Stuart Douglas (JIRA)

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (WELD-1080) Fix licence headers

by Martin Kouba (JIRA)

Martin Kouba created WELD-1080: ---------------------------------- Summary: Fix licence headers Key: WELD-1080 URL: https://issues.jboss.org/browse/WELD-1080 Project: Weld Issue Type: Bug Reporter: Martin Kouba Assignee: Ales Justin Priority: Minor A lot of files in Weld (all branches) uses wrong licence header (LGPL instead of ASL2). -- 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

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (WELD-1157) Bean creation is blocked across all threads until method annotated with @PostConstruct has finished

by Vetle Roeim (JIRA)

11 years, 9 months

4
5
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] (WELD-1123) WELD-000075 error message with AspectJ

by Jean ANDRE (JIRA)

Jean ANDRE created WELD-1123: -------------------------------- Summary: WELD-000075 error message with AspectJ Key: WELD-1123 URL: https://issues.jboss.org/browse/WELD-1123 Project: Weld Issue Type: Bug Affects Versions: 1.1.4.Final Environment: WELD-000900 1.1.4 (Final) with GlassFish 3.1.2 Open Source - commons-lang-2.4 - commons-logging-1.1.1 - cssparser-0.9.6 - el-impl-2.2 - guava-11.0.1 - hibernate-validator-4.2.0.Final - junit-4.10 - log4j-1.2.16 - richfaces-components-api-4.2.1.Final - sac-1.3 - AspectJ / AJDT for Eclipse Indigo. Reporter: Jean ANDRE We have an application - Without AspectJ, the application is running smoothly but as soon as we activate aspectJ, if we tried to deploy and run the application we got the following error message: {code} GRAVE: Exception while loading the app GRAVE: Exception while loading the app : WELD-000075 Normal scoped managed bean implementation class has a public field: public@Named @RequestScoped class com.nested.web.controller.PanelTwoController org.jboss.weld.exceptions.DefinitionException: WELD-000075 Normal scoped managed bean implementation class has a public field: public@Named @RequestScoped class com.nested.web.controller.PanelTwoController at org.jboss.weld.bean.ManagedBean.checkBeanImplementation(ManagedBean.java:438) at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:191) at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:322) at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:115) at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:204) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:344) at org.glassfish.weld.WeldDeployer.event(WeldDeployer.java:179) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:277) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:460) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348) {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

11 years, 9 months

3
28
0 / 0

[JBoss JIRA] (WELD-1169) ConcurrentBeanDeployer may trigger JVM deadlock

by Jozef Hartinger (JIRA)

11 years, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2012