March 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1078) BeanManager#createInjectionPoint - IllegalArgumentException not thrown if there is a definition error associated with the injection point

by Martin Kouba (JIRA)

Martin Kouba created WELD-1078: ---------------------------------- Summary: BeanManager#createInjectionPoint - IllegalArgumentException not thrown if there is a definition error associated with the injection point Key: WELD-1078 URL: https://issues.jboss.org/browse/WELD-1078 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha1 Reporter: Martin Kouba Assignee: Jozef Hartinger *11.3.21. Obtaining an InjectionPoint*: "The method BeanManager.createInjectionPoint() returns a container provided implementation of InjectionPoint for a given AnnotatedField or AnnotatedParameter or throws an IllegalArgumentException if there is a definition error associated with the injection point." See TCK 1.1 tests: *org.jboss.cdi.tck.tests.extensions.beanManager.injectionPoint.CreateInjectionPointTest.testInvalidParameter()* *org.jboss.cdi.tck.tests.extensions.beanManager.injectionPoint.CreateInjectionPointTest.testInvalidField()* -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (WELD-987) Misleading definition error for decorator with observer method

by Martin Kouba (Created) (JIRA)

Misleading definition error for decorator with observer method -------------------------------------------------------------- Key: WELD-987 URL: https://issues.jboss.org/browse/WELD-987 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Environment: JBoss AS7 Reporter: Martin Kouba Priority: Minor CDI 1.0 section 10.4.2 states: "Interceptors and decorators may not declare observer methods. If an interceptor or decorator has a method with a paramet- er annotated @Observes, the container automatically detects the problem and treats it as a definition error." Following definition error is detected for decorator with observer method: *WELD-001419 - DECORATOR_CLASS_NOT_BEAN_CLASS_OF_DECORATOR* New definition error like *DECORATORS_CANNOT_HAVE_OBSERVER_METHODS* would be more appropriate. TCK test for this scenario (CDI 1.1 master branch): https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- 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, 7 months

6
6
0 / 0

[JBoss JIRA] Created: (WELD-920) Memory leak through the creational context of an @AppScoped bean when injecting Instance<>

by Adam Warski (JIRA)

Memory leak through the creational context of an @AppScoped bean when injecting Instance<> ------------------------------------------------------------------------------------------ Key: WELD-920 URL: https://issues.jboss.org/browse/WELD-920 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.1.Final, 1.1.0.CR3 Reporter: Adam Warski Given a simple dependent-scoped bean: public class InstanceBean {}, and an application-scoped bean (see below) to which an instance of the dependent-scoped bean is injected, each time the get() method is called on the instance, even though it's not used, a reference to it stays in the creational context of the application scoped bean (http://screencast.com/t/XqjQ1GB7Wv3). That way after several requests, where each one calls the method, more and more memory is leaked (http://screencast.com/t/s1VBx49i). Attached is a simple web application demonstrating this. To reproduce, deploy to AS6, click the "leak" button several times, and analyze the heap dump e.g. in JProfiler. @ApplicationScoped @Named("test") public class AppScopedBean { private Instance<InstanceBean> instanceBeanInstance; @Inject public AppScopedBean(Instance<InstanceBean> instanceBeanInstance) { this.instanceBeanInstance = instanceBeanInstance; } public AppScopedBean() { } public void leakOneInstance() { System.out.println("Leaked!"); instanceBeanInstance.get(); } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
17
0 / 0

[JBoss JIRA] (WELD-1024) Missing check that specializing bean has all the bean types of specialized bean

by Martin Kouba (Created) (JIRA)

Missing check that specializing bean has all the bean types of specialized bean ------------------------------------------------------------------------------- Key: WELD-1024 URL: https://issues.jboss.org/browse/WELD-1024 Project: Weld Issue Type: Bug Reporter: Martin Kouba Spec *4.3.1. Direct and indirect specialization* states: "Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y, the container automatically detects the problem and treats it as a definition error." However definition error is not detected and application is deployed in corrupted state. -- 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, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (WELD-510) Support for Portlet 2.0

by Neil Griffin (JIRA)

Support for Portlet 2.0 ----------------------- Key: WELD-510 URL: https://jira.jboss.org/jira/browse/WELD-510 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.1.Final Reporter: Neil Griffin There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue. Original Post: http://www.portletfaces.org/community/forums/-/message_boards/message/430... Here is a simple stacktrace of the problem: Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119) at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener The code for the bridge API is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... The code for the bridge IMPL is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... And the code for a sample portlet is here: http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-... -- 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

12 years, 7 months

12
36
0 / 0

[JBoss JIRA] (CDITCK-266) Provide the porting package javadoc as part of the CDI TCK bundle

by Martin Kouba (JIRA)

Martin Kouba created CDITCK-266: ----------------------------------- Summary: Provide the porting package javadoc as part of the CDI TCK bundle Key: CDITCK-266 URL: https://issues.jboss.org/browse/CDITCK-266 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.0.5.CR1, 1.1.0.Alpha2 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] (WELD-1069) Parallelize Weld bootstrap

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1069: ------------------------------------- Summary: Parallelize Weld bootstrap Key: WELD-1069 URL: https://issues.jboss.org/browse/WELD-1069 Project: Weld Issue Type: Task Affects Versions: 2.0.0.Alpha1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Blocker Fix For: 2.0.0.Alpha2 -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] (WELD-1049) BeanManager.createInjectionTarget() does not support interception

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1049: ------------------------------------- Summary: BeanManager.createInjectionTarget() does not support interception Key: WELD-1049 URL: https://issues.jboss.org/browse/WELD-1049 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Ales Justin Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 SimpleInjectionTarget does not have support for interceptors nor decorators. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] (WELD-1097) Event of array type fired via built-in Event bean is not observed

by Martin Kouba (JIRA)

Martin Kouba created WELD-1097: ---------------------------------- Summary: Event of array type fired via built-in Event bean is not observed Key: WELD-1097 URL: https://issues.jboss.org/browse/WELD-1097 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha1, 1.1.5.Final Reporter: Martin Kouba See also https://github.com/weld/core/pull/187 When firing event via built-in Event bean Weld gets the event type information through reflection and the problem seems to be in {{org.jboss.weld.bean.builtin.AbstractFacade.getFacadeType()}} method. For example for this injection point {code} @Inject Event<Foo[]> fooEvent; {code} the result of the call to getActualTypeArguments()[0] is GenericArrayType with component type Foo (not sure why... I'd expect it to be Class). -- 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, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (CDITCK-204) TCK Harness property configuration broken

by Sivakumar Thyagarajan (JIRA)

TCK Harness property configuration broken ----------------------------------------- Key: CDITCK-204 URL: https://issues.jboss.org/browse/CDITCK-204 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sivakumar Thyagarajan As per http://docs.jboss.org/cdi/tck/reference/latest/en-US/html/test-harness-co..., a custom ConfigurationBuilder or an implementation of the SPI class such as org.jboss.jsr299.tck.spi.Beans could be provided by the TCK executor through a system property specifying the FQCN of the implementation class. However while trying to plug in a custom Beans SPI implementation or a ConfigurationBuilder using the system property, the default PropertiesBasedConfigurationBuilder seems to collate [1] all the properties file in the classpath and include the default implementations (bundled in the porting package or harness) as well. > [testng] Exception in thread "main" java.lang.IllegalArgumentException: More than one implementation of Beans specified by org.jboss.jsr299.tck.spi.Beans, not sure which one to use! > [testng] at org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:159) > [testng] at org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169) > [testng] at org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62) This prevents configuration of the TCK to use a custom SPI class implementation and/or ConfigurationBuilder. The only workaround seems to be providing a modified version of the existing porting package class and ensuring that it is loaded ahead. [1] [1] http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2012