November 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-750) German translation of Weld Reference Documentation

by Thorsten Spaeth (JIRA)

German translation of Weld Reference Documentation -------------------------------------------------- Key: WELD-750 URL: https://jira.jboss.org/browse/WELD-750 Project: Weld Issue Type: Task Components: Documentation Reporter: Thorsten Spaeth Priority: Trivial Fix For: TBC I am currently starting to translate the Weld Reference Documentation to German (de-DE). I'd like to contribute that bit by bit to the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (CDITCK-191) double slash in Converstaion test urls break redirect

by David Jencks (JIRA)

double slash in Converstaion test urls break redirect ----------------------------------------------------- Key: CDITCK-191 URL: https://jira.jboss.org/browse/CDITCK-191 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: David Jencks The Conversation tests all call AbstractConversationTest.getPath() with strings starting with / such as /storm.jspx. Since the method tacks a / at the end of the context root you end up with urls for the form foo//bar.jsf. While tomcat appears to think that this is the same url as foo/bar.jsf, jetty doesn't. This breaks the redirect in LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedOverRedirect. Removing the / from the arguments to getPath fixes the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
13
0 / 0

[JBoss JIRA] Created: (CDITCK-186) TCK does not properly test for inhertance of observer methods

by Igor Vaynberg (JIRA)

TCK does not properly test for inhertance of observer methods ------------------------------------------------------------- Key: CDITCK-186 URL: https://jira.jboss.org/browse/CDITCK-186 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Igor Vaynberg EventTest has a bug in it. According to section 4.2 of the spec {code} If X declares an initializer, non-static observer, @PostConstruct or @PreDestroy method x() then Y inherits x() if and only if neither Y nor any intermediate class that is a subclass of X and a superclass of Y overrides the method x(). {code} both IntermediateStockWatcher and IndirectStockWatcher which extend StockWatcher should inherit its observer method: {code} StockWatcher#public void observeStockPrice(@Observes StockPrice price) {code} However, EventTest on line 149 asserts there is only one observer method, when in fact there should be three: {code} 147: StockPrice price = new StockPrice(); 148: Set<ObserverMethod<? super StockPrice>> observers = getCurrentManager().resolveObserverMethods(price); 149: assert observers.size() == 1; {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (WELD-762) ThreadLocal leak with Weld Servlet

by Aslak Knutsen (JIRA)

ThreadLocal leak with Weld Servlet ---------------------------------- Key: WELD-762 URL: https://jira.jboss.org/browse/WELD-762 Project: Weld Issue Type: Bug Components: Servlet Container Support Reporter: Aslak Knutsen Nov 22, 2010 7:13:40 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [/active1] created a ThreadLocal with key of type [null] (value [org.jboss.weld.injection.CurrentInjectionPoint$1@30b95f2]) and a value of type [java.util.Stack] (value [[]]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak. Weld Servlet 1.1.0-SNAPSHOT / Beta2 / Beta1 on Tomcat 6 Not sure if this is Weld Servlet or Weld Core. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (CDITCK-193) CDI TCK version 1.0.2.CR3 is missing a depoendency jar - arquillian-weld-ee-embedded-1.1-1.1.0.Beta2.jar

by Kyle Grucci (JIRA)

CDI TCK version 1.0.2.CR3 is missing a depoendency jar - arquillian-weld-ee-embedded-1.1-1.1.0.Beta2.jar -------------------------------------------------------------------------------------------------------- Key: CDITCK-193 URL: https://jira.jboss.org/browse/CDITCK-193 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Environment: All Reporter: Kyle Grucci The org.jboss.weld.atinject.tck.AtInjectTCK appears in the CDI TCK bundle (version 1.0.2.CR3) in weld/porting-package-lib/weld-inject-tck-runner-tests.jar, and this class now has a new dependency on org/jboss/arquillian/container/weld/ee/embedded_1_1/mock/TestContainer . This class should also be included in the TCK bundle to satisfy this dependency. We use the org.jboss.weld.atinject.tck.AtInjectTCK class when running the JSR 330 TCK against Glassfish (which includes Weld). Adding this jar seemd so get by the problem... https://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/a... Thanks, Pete for sending this pointer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-770) Intercepting a bean with constructor injection causes an InstantiationException

by Adam Warski (JIRA)

Intercepting a bean with constructor injection causes an InstantiationException ------------------------------------------------------------------------------- Key: WELD-770 URL: https://jira.jboss.org/browse/WELD-770 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Beta2 Reporter: Adam Warski Used to work fine until AS6 CR1 (tested in M2 and M4). Stack trace: org.jboss.arquillian.impl.event.FiredEventException: java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:97) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:443) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:160) at org.testng.internal.Invoker.invokeMethod(Invoker.java:494) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:908) at org.testng.TestRunner.privateRun(TestRunner.java:617) at org.testng.TestRunner.run(TestRunner.java:498) at org.testng.SuiteRunner.runTest(SuiteRunner.java:329) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:324) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:296) at org.testng.SuiteRunner.run(SuiteRunner.java:201) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:75) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:92) Caused by: java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:103) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:52) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:42) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:32) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 27 more Caused by: org.jboss.weld.exceptions.DeploymentException: pl.softwaremill.weldbugs.bug3.org$jboss$weld$bean-c545a346-00cf-487d-9f47-7f2cbd100daf$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug3$TestBean3_2_$$_WeldProxy at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:569) at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.produce(ManagedBean.java:250) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:332) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:59) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:669) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:743) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:137) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:869) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:881) at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:122) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:54) at org.jboss.weld.manager.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:116) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:113) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:93) ... 31 more Caused by: org.jboss.weld.exceptions.DefinitionException: pl.softwaremill.weldbugs.bug3.org$jboss$weld$bean-c545a346-00cf-487d-9f47-7f2cbd100daf$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug3$TestBean3_2_$$_WeldProxy at org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:224) at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:564) ... 44 more Caused by: java.lang.InstantiationException: pl.softwaremill.weldbugs.bug3.org$jboss$weld$bean-c545a346-00cf-487d-9f47-7f2cbd100daf$jar-ManagedBean-class_pl$softwaremill$weldbugs$bug3$TestBean3_2_$$_WeldProxy at java.lang.Class.newInstance0(Class.java:340) at java.lang.Class.newInstance(Class.java:308) at org.jboss.weld.util.reflection.SecureReflections$16.work(SecureReflections.java:396) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInstantiation(SecureReflectionAccess.java:216) at org.jboss.weld.util.reflection.SecureReflections.newInstance(SecureReflections.java:391) at org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:219) ... 45 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-771) Interception of beans with final methods causes final methods to be invoked on the proxy

by Stuart Douglas (JIRA)

Interception of beans with final methods causes final methods to be invoked on the proxy ---------------------------------------------------------------------------------------- Key: WELD-771 URL: https://jira.jboss.org/browse/WELD-771 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta2 Reporter: Stuart Douglas Fix For: 1.1.0.Beta3 We currently allow method level interceptors on beans that also have private methods, which causes the final methods to be invoked on the proxy. There are two options here: - Fix WELD-437 (implement interception through subclassing) - Pick this up in the verification phase and either log a warning or throw an exception -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-705) Changes made to a superclass's AnnotatedType by extensions not taken into account while sending ProcessAnnotatedType events pertaining to the subclass

by Sivakumar Thyagarajan (JIRA)

Changes made to a superclass's AnnotatedType by extensions not taken into account while sending ProcessAnnotatedType events pertaining to the subclass ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: WELD-705 URL: https://jira.jboss.org/browse/WELD-705 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.0.Beta1 Environment: Jersey extension in GlassFish faces this issue Reporter: Sivakumar Thyagarajan Fix For: 1.1.0.Beta2 It appears that Weld does not take into account changes made to a superclass's AnnotatedType by extensions, when sending ProcessAnnotatedType events pertaining to the subclass. Please find attached a netbeans project that demonstrates the problem. It is a web app containing a CDI extension that patches the annotated types it sees to remove all their fields. BeanOne has one field: @Inject BeanManager beanManager; BeanTwo extends BeanOne and doesn't add any fields. There are no other injection points. The portable extensions patches the annotated type for BeanOne and removes the BeanManager injection point. However on execution, this output appears in the server log: (all the diagnostic output is at warning level...) === WARNING: Handling BeforeBeanDiscovery event WARNING: Handling ProcessAnnotatedType event for beans.BeanOne WARNING: type has 0 fields WARNING: replaced annotated type for class beans.BeanOne WARNING: Handling ProcessAnnotatedType event for beans.BeanTwo WARNING: type has 0 fields WARNING: replaced annotated type for class beans.BeanTwo WARNING: Handling ProcessManagedBean event for beans.BeanTwo WARNING: found injection point interface javax.enterprise.inject.spi.BeanManager @javax.enterprise.inject.Default() WARNING: Handling ProcessManagedBean event for beans.BeanOne === I.e. in BeanOne the field has been correctly nuked, but it comes back in BeanTwo. Weld may be holding a reference to the old AnnotatedType for BeanOne as part of its internal representation for BeanTwo and uses that instead of the replacement provided by the extension. Since annotated types are self-contained, so Weld should not even look at BeanOne at that point. The same behavior can be observed on both GF 3.0.1 (=WELD-000900 1.0.1 (SP3)) and GF 3.1-b16 (=WELD-000900 1.1.0.01 (glassfish)). A glassfish issue tracking this Jersey extension problem is at https://glassfish.dev.java.net/issues/show_bug.cgi?id=13132 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (WELD-711) Calling Contextual.destroy on an instance still references an instance on BeanManager

by George Gastaldi (JIRA)

Calling Contextual.destroy on an instance still references an instance on BeanManager ------------------------------------------------------------------------------------- Key: WELD-711 URL: https://jira.jboss.org/browse/WELD-711 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.0.Beta1, 1.0.1.Final Reporter: George Gastaldi Attachments: report.txt Using the seam-faces module @ViewScoped extension, when the object is destroyed by Contextual.destroy, weld still references an instance, avoiding being garbage-collected. {code} Contextual contextual = ... Object instance = ... CreationalContext creational = ... contextual.destroy(instance, creational); {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
28
0 / 0

[JBoss JIRA] Created: (WELD-437) Use subclasses for interceptors and decorators

by Pete Muir (JIRA)

Use subclasses for interceptors and decorators ---------------------------------------------- Key: WELD-437 URL: https://jira.jboss.org/jira/browse/WELD-437 Project: Weld Issue Type: Bug Reporter: Pete Muir Priority: Critical Fix For: 1.0.2.CR1 -- 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

13 years, 11 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues November 2010