March 2009 - weld-issues - Jboss List Archives

[webbeans-issues] [JBoss JIRA] Created: (WBRI-205) Non-business producer methods in a Session bean do not throw a DefinitionException on deployment

by Shane Bryzak (JIRA)

Non-business producer methods in a Session bean do not throw a DefinitionException on deployment ------------------------------------------------------------------------------------------------ Key: WBRI-205 URL: https://jira.jboss.org/jira/browse/WBRI-205 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak Section 3.4.2 of the spec states: "If a non-static method of a session bean class is annotated @Produces, and the method is not a business method of the EJB, a DefinitionException is thrown by the container at deployment time." Test org.jboss.jsr299.tck.tests.implementation.producer.method.enterprise.nonbusiness.ProducerMethodNotBusinessMethodTest() is successfully deploying without an exception being raised. -- 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

15 years, 2 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-203) Inherited @PostConstruct on session bean not invoked

by Shane Bryzak (JIRA)

Inherited @PostConstruct on session bean not invoked ---------------------------------------------------- Key: WBRI-203 URL: https://jira.jboss.org/jira/browse/WBRI-203 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak In section 4.2 the spec states: "Suppose a class X is the bean class of a simple or session bean Y declared using XML. <snip> • If X declares an initializer method, @PostConstruct method or @PreDestroy method x() then Y inherits x(), unless Y explicitly declares x() using XML." The @PostConstruct method does not seem be be invoked on session beans that extend a superclass with a @PostConstruct method declared. See TCK test org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testIndirectSubClassInheritsPostConstructOnSuperclass() -- 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

15 years, 2 months

1
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-195) application context isn't thread safe

by Takeshi Kondo (JIRA)

application context isn't thread safe ------------------------------------- Key: WBRI-195 URL: https://jira.jboss.org/jira/browse/WBRI-195 Project: Web Beans Issue Type: Bug Components: Contexts Affects Versions: 1.0.0.BETA1 Reporter: Takeshi Kondo Assignee: Nicklas Karlsson Application scoped object initialization isn't synchronized. so if initialization in concurrent request , create more than one instance. -- 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

15 years, 2 months

3
8
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-144) Producer methods on specialized beans are being deployed

by Pete Muir (JIRA)

Producer methods on specialized beans are being deployed -------------------------------------------------------- Key: WBRI-144 URL: https://jira.jboss.org/jira/browse/WBRI-144 Project: Web Beans RI Issue Type: Bug Reporter: Pete Muir Fix For: 1.0.0.BETA2 -- 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

15 years, 2 months

1
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-157) Rewrite bean deployer to order beans before initialization, allowing use of existing beans for beans which require another bean (e.g. producer methods, disposal methods, specialization)

by Pete Muir (JIRA)

Rewrite bean deployer to order beans before initialization, allowing use of existing beans for beans which require another bean (e.g. producer methods, disposal methods, specialization) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: WBRI-157 URL: https://jira.jboss.org/jira/browse/WBRI-157 Project: Web Beans Issue Type: Task Reporter: Pete Muir Assignee: Pete Muir Priority: Blocker Fix For: 1.0.0.BETA2 -- 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

15 years, 2 months

1
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-116) Support specializing producer methods on enterprise beans

by Pete Muir (JIRA)

Support specializing producer methods on enterprise beans --------------------------------------------------------- Key: WBRI-116 URL: https://jira.jboss.org/jira/browse/WBRI-116 Project: Web Beans RI Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.0.BETA1 Deferring for now, as really we need a "better" bean deployer to support this (one that order bean creation so that the specialized bean is created and available for the specializing bean to use). This intersects with XML deployment. -- 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

15 years, 2 months

1
4
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-52) jBPM integration

by Gavin King (JIRA)

jBPM integration ---------------- Key: WBRI-52 URL: https://jira.jboss.org/jira/browse/WBRI-52 Project: Web Beans RI Issue Type: Feature Request Reporter: Gavin King Priority: Minor -- 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

15 years, 2 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-50) Seam integration

by Gavin King (JIRA)

Seam integration ---------------- Key: WBRI-50 URL: https://jira.jboss.org/jira/browse/WBRI-50 Project: Web Beans RI Issue Type: Feature Request Reporter: Gavin King Priority: Minor -- 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

15 years, 2 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-173) Instance.get() is passing @Obtains binding type to Manager.getInstanceByType()

by Shane Bryzak (JIRA)

Instance.get() is passing @Obtains binding type to Manager.getInstanceByType() ------------------------------------------------------------------------------ Key: WBRI-173 URL: https://jira.jboss.org/jira/browse/WBRI-173 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak Fix For: 1.0.0.BETA2 Section 5.8 of the spec states: " The get() method of the provided implementation of Instance must call Manager.getInstanceByType(), passing the following parameters: * all bindings declared at the injection point, except @Obtains" It seems to be passing the @Obtains binding as well, as evidenced by the following test failure: javax.inject.UnsatisfiedDependencyException: class sun.reflect.generics.reflectiveObjects.TypeVariableImpl; binding types = [@Obtains, @PayBy]Unable to resolve any Web Beans at org.jboss.webbeans.ManagerImpl.getBeanByType(ManagerImpl.java:755) at org.jboss.webbeans.ManagerImpl.getInstanceByType(ManagerImpl.java:747) at org.jboss.webbeans.ManagerImpl.getInstanceByType(ManagerImpl.java:718) at org.jboss.webbeans.InstanceImpl.get(InstanceImpl.java:60) at org.jboss.jsr299.tck.tests.lookup.dynamic.DynamicLookupTest.testObtainsAllowsAdditionalBindings(DynamicLookupTest.java:38) -- 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

15 years, 3 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-156) Redo architectore for facade beans

by Pete Muir (JIRA)

Redo architectore for facade beans ----------------------------------- Key: WBRI-156 URL: https://jira.jboss.org/jira/browse/WBRI-156 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Priority: Critical Fix For: 1.0.0.BETA2 These are totally wrong - they are facades, so there should be one bean per facade, not one bean per facade instance! -- 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

15 years, 3 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2009