March 2009 - weld-issues - Jboss List Archives

[webbeans-issues] [JBoss JIRA] Created: (WBRI-210) Destroyed beans not removed from normal contexts

by David Allen (JIRA)

Destroyed beans not removed from normal contexts ------------------------------------------------ Key: WBRI-210 URL: https://jira.jboss.org/jira/browse/WBRI-210 Project: Web Beans Issue Type: Bug Components: Contexts Affects Versions: 1.0.0.BETA1 Reporter: David Allen Assignee: Nicklas Karlsson Whenever a contextual bean is destroyed, that instance is not to be returned again by the context on later calls to get() per section 8.1 of JSR-299 specification. The current specification does not actually provide any API to remove the instance from a context. Since any application can add additional contexts, there needs to be a specific API to allow the destroyed beans to removed or to otherwise notify the corresponding context that a bean has been destroyed. The test which is currently marked ri-broken is DestroyedInstanceReturnedByGetTest.testDestroyedInstanceMustNotBeReturnedByGet(). -- 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, 9 months

1
1
0 / 0

[webbeans-issues] [JBoss JIRA] Closed: (WBINT-9) Switch to using bootstrap.getServiceRegistery().add(type, impl)

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/WBINT-9?page=com.atlassian.jira.plugin... ] Pete Muir closed WBINT-9. ------------------------- Resolution: Done Assignee: Pete Muir (was: Ales Justin) > Switch to using bootstrap.getServiceRegistery().add(type, impl) > --------------------------------------------------------------- > > Key: WBINT-9 > URL: https://jira.jboss.org/jira/browse/WBINT-9 > Project: Web Beans Integration > Issue Type: Feature Request > Components: Deployer > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 5.2.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, 9 months

1
0
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-172) Classes marked with @Entity should not be discovered as simple beans

by Shane Bryzak (JIRA)

Classes marked with @Entity should not be discovered as simple beans -------------------------------------------------------------------- Key: WBRI-172 URL: https://jira.jboss.org/jira/browse/WBRI-172 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak Fix For: 1.0.0.BETA2 The spec states "A top-level Java class is not a simple bean if it is annotated with the JPA @Entity annotation" however classes with the @Entity annotation are being discovered. Please see TCK test org.jboss.jsr299.tck.tests.implementation.simple.definition.SimpleBeanDefinition.testEntityClassesNotDiscoveredAsSimpleBean() -- 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, 9 months

3
5
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-169) Bean type with type variable throws incorrect exception on deployment

by Shane Bryzak (JIRA)

Bean type with type variable throws incorrect exception on deployment --------------------------------------------------------------------- Key: WBRI-169 URL: https://jira.jboss.org/jira/browse/WBRI-169 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak Fix For: 1.0.0.BETA2 Section 2.2 of the spec says: "Bean types may not declare a type variable. If the type of an injection point is a parameterized type with a type variable, a DefinitionException is thrown by the container at deployment time." The TCK tests org.jboss.jsr299.tck.tests.definition.deployment.broken.typevariable.ParameterizedTypeInjectionTest and org.jboss.jsr299.tck.tests.definition.deployment.broken.wildcard.WilcardTypeInjectionTest should be throwing a DefinitionException at deployment time, however are throwing an UnsatisfiedDependencyException instead (tests are currently marked as ri-broken). -- 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, 9 months

3
9
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-51) Spring integration

by Gavin King (JIRA)

Spring integration ------------------ Key: WBRI-51 URL: https://jira.jboss.org/jira/browse/WBRI-51 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, 9 months

2
5
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-136) Observer method resolution ignores type parameters

by David Allen (JIRA)

Observer method resolution ignores type parameters -------------------------------------------------- Key: WBRI-136 URL: https://jira.jboss.org/jira/browse/WBRI-136 Project: Web Beans RI Issue Type: Bug Affects Versions: 1.0.0.ALPHA2 Reporter: David Allen Assignee: David Allen Priority: Minor Section 7.7 of the PRD2 specification states: When searching for observers for an event, the container searches for observers which satisfy the following rules: • the event object must be assignable to the observed event type, taking type parameters into consideration, and ... Currently resolution works only for the event type information, regardless of any specific type parameters. The test for this assertion is in org.jboss.jsr299.tck.unit.event.EventTest.testResolvingChecksTypeParameters(). -- 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, 9 months

2
5
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-206) Tidy up usage of isSerializable

by Pete Muir (JIRA)

Tidy up usage of isSerializable ------------------------------- Key: WBRI-206 URL: https://jira.jboss.org/jira/browse/WBRI-206 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.0.PREVIEW -- 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, 9 months

1
1
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-194) super class and interfaces don't inherit type parameters.

by Takeshi Kondo (JIRA)

super class and interfaces don't inherit type parameters. --------------------------------------------------------- Key: WBRI-194 URL: https://jira.jboss.org/jira/browse/WBRI-194 Project: Web Beans Issue Type: Bug Components: Producer beans Affects Versions: 1.0.0.BETA1 Reporter: Takeshi Kondo Attachments: parameterized_type_inheritance.patch, test_code.patch for instance @Produces public List<String> createStringList() { return Arrays.asList("aaa", "bbb"); } I expected that this producer method is bound to List<String> and Collection<String>... . but actual bound type is List<String> and Collection ... . -- 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, 9 months

2
5
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-193) resolve potential LinkageError

by Takeshi Kondo (JIRA)

resolve potential LinkageError ------------------------------ Key: WBRI-193 URL: https://jira.jboss.org/jira/browse/WBRI-193 Project: Web Beans Issue Type: Patch Affects Versions: 1.0.0.BETA1 Reporter: Takeshi Kondo Priority: Trivial Some time age, LinkageError is caused by Seam's Javassist ProxyFactory usage. It same applies to WebBeans. if possible, make a modification from --- ProxyFactory proxyFactory = new ProxyFactory(); proxyFactory.setSuperclass(getSuperClass(); proxyFactory.setInterfaces(getInterfaces()); return proxyFactory; to --- ProxyFactory proxyFactory = new ProxyFactory(); Class<?> superClass = getSuperClass(); if(superClass != Object.class) { proxyFactory.setSuperclass(superClass); } proxyFactory.setInterfaces(getInterfaces()); return proxyFactory; --- Apply to this patch, If proxy target class is interface, generated proxy class name changes form "org.javassist.tmp.java.lang.Object_$$_javassist_0" to "org.javassist.tmp.java.util.List_$$_javassist_0". All interface generated proxy class name is "org.javassist.tmp.java.lang.Object_$$_javassist_(number)" Because proxy class name pattern is monotone, duplicate proxy class name, then it causes LinkageError. -- 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, 9 months

2
9
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-162) Use ResolvableAnnotatedClass in resolveObserver

by Pete Muir (JIRA)

Use ResolvableAnnotatedClass in resolveObserver ----------------------------------------------- Key: WBRI-162 URL: https://jira.jboss.org/jira/browse/WBRI-162 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir Assignee: David Allen 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, 9 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2009