December 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-312) AroundInvoke annotation is not honoured by SPI

by Stuart Douglas (JIRA)

AroundInvoke annotation is not honoured by SPI ---------------------------------------------- Key: WELD-312 URL: https://jira.jboss.org/jira/browse/WELD-312 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Stuart Douglas When registering interceptors using the SPI weld ignores the information passed in via the AnnotatedMethod object and instead looks for the AroundInvoke annotation using reflection. -- 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

14 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (WELD-337) Unable to run cdi-tck (dist) tests against JBoss AS 6.0.x

by Martin Gencur (JIRA)

Unable to run cdi-tck (dist) tests against JBoss AS 6.0.x --------------------------------------------------------- Key: WELD-337 URL: https://jira.jboss.org/jira/browse/WELD-337 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Martin Gencur Priority: Critical Fix For: 1.0.1.CR1 cdi-tck tests are executed in this job: http://hudson.qa.jboss.com/hudson/view/Weld/job/Weld-tck-dist-incontainer... Last successfull build is taken from JBossAS 6.0.x job and jsr299-tck-1.0.0-dist.zip is used. After starting the test run, the following exception is thrown (Cannot find any implementations of TestLauncher, check that org.jboss.testharness.api.TestLauncher is specified) : 16:42:04,214 INFO [htmlunit.WebClient] statusCode=[500] contentType=[text/html] 16:42:04,214 INFO [htmlunit.WebClient] <html><head><title>JBoss Web/3.0.0.alpha-22 - Error report</title><style></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade">type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception <pre>javax.servlet.ServletException: Cannot find any implementations of TestLauncher, check that org.jboss.testharness.api.TestLauncher is specified javax.faces.webapp.FacesServlet.service(FacesServlet.java:323) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) </pre>root cause <pre>java.lang.IllegalArgumentException: Cannot find any implementations of TestLauncher, check that org.jboss.testharness.api.TestLauncher is specified org.jboss.testharness.properties.PropertiesManager.getClassValue(PropertiesManager.java:150) org.jboss.testharness.properties.PropertiesManager.getInstanceValue(PropertiesManager.java:169) org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.getInstanceValue(PropertiesBasedConfigurationBuilder.java:62) org.jboss.testharness.impl.PropertiesBasedConfigurationBuilder.init(PropertiesBasedConfigurationBuilder.java:53) org.jboss.jsr299.tck.impl.JSR299PropertiesBasedConfigurationBuilder.init(JSR299PropertiesBasedConfigurationBuilder.java:33) org.jboss.jsr299.tck.impl.JSR299PropertiesBasedConfigurationBuilder.init(JSR299PropertiesBasedConfigurationBuilder.java:16) org.jboss.testharness.impl.ConfigurationFactory.get(ConfigurationFactory.java:22) org.jboss.jsr299.tck.tests.context.conversation.client.ConversationTestPhaseListener.beforePhase(ConversationTestPhaseListener.java:34) com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:110) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) javax.faces.webapp.FacesServlet.service(FacesServlet.java:310) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:68) </pre>note The full stack trace of the root cause is available in the JBoss Web/3.0.0.alpha-22 logs.<HR size="1" noshade="noshade"><h3>JBoss Web/3.0.0.alpha-22</h3></body></html> This exception causes almost all the tests fail. I tried to run this job locally with the same result. org.jboss.testharness.api.TestLauncher property is really specified in a file jsr299/weld/jboss-tck-runner/src/main/resources/META-INF/jboss-test-harness.properties (and jsr299/weld/jboss-tck-runner/target/classes/META-INF/jboss-test-harness.properties) and the implementation of the TestLauncher is in directory jsr299/lib/jboss-test-harness.jar -- 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

14 years, 10 months

3
18
0 / 0

[JBoss JIRA] Created: (WELD-335) RIBean needs new definition of equality

by Stuart Douglas (JIRA)

RIBean needs new definition of equality --------------------------------------- Key: WELD-335 URL: https://jira.jboss.org/jira/browse/WELD-335 Project: Weld Issue Type: Bug Components: Built-in beans Reporter: Stuart Douglas Attachments: ri-bean-id-creator.patch Due to the implementation of equals/hashCode in RIBean only one ManagedBean is allowed per underlying java class, so for example if you use the SPI to add two AnnotatedTypes with the same underlying class but different qualifiers only one will get installed. The following patch fixes this, would it be possible to get some feedback on it? The AnnotatedTypeIdProvider class in the patch can also be used to implement meaningful equlity for WeldAnnotated* -- 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

14 years, 10 months

2
23
0 / 0

[JBoss JIRA] Created: (WELD-309) Alter equality for AnnotatedType so you can have >1 AnnotatedType for

by Pete Muir (JIRA)

Alter equality for AnnotatedType so you can have >1 AnnotatedType for ---------------------------------------------------------------------- Key: WELD-309 URL: https://jira.jboss.org/jira/browse/WELD-309 Project: Weld Issue Type: Bug Components: Reflection layer Reporter: Pete Muir Fix For: 1.0.1.CR1 Currently we use the underlying class to perform equality, this is wrong. -- 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

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (WELD-272) DefinitionError thrown when a decorated bean is final or has final method (should be DeploymentError)

by Jozef Hartinger (JIRA)

DefinitionError thrown when a decorated bean is final or has final method (should be DeploymentError) ----------------------------------------------------------------------------------------------------- Key: WELD-272 URL: https://jira.jboss.org/jira/browse/WELD-272 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.GA org.jboss.jsr299.tck.tests.decorators.definition.broken.finalBeanClass.FinalBeanClassTest.testAppliesToFinalManagedBeanClass() org.jboss.jsr299.tck.tests.decorators.definition.broken.finalBeanMethod.FinalBeanMethodTest.testAppliesToFinalMethodOnManagedBeanClass() -- 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

14 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (WELD-274) Deployment problem not detected when a custom decorator can decorate final bean

by Jozef Hartinger (JIRA)

Deployment problem not detected when a custom decorator can decorate final bean ------------------------------------------------------------------------------- Key: WELD-274 URL: https://jira.jboss.org/jira/browse/WELD-274 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Interceptors and Decorators Affects Versions: 1.0.0.CR1 Reporter: Jozef Hartinger Fix For: 1.0.0.GA org.jboss.jsr299.tck.tests.decorators.custom.broken.finalBeanClass.CustomDecoratorMatchingBeanWithFinalClassTest.testCustomDecoratorDecoratingFinalBean() -- 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

14 years, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (WELD-291) Decorator @Delegate injection points cause unsatisfied and ambiguous dependencies

by Gavin King (JIRA)

Decorator @Delegate injection points cause unsatisfied and ambiguous dependencies --------------------------------------------------------------------------------- Key: WELD-291 URL: https://jira.jboss.org/jira/browse/WELD-291 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.GA Reporter: Gavin King Priority: Critical Fix For: 1.0.1.CR1 A decorator delegate injection point should not be validated for unsatisfied or ambiguous dependencies. Currently Weld fails at startup when a decorator applies to either 0 or more than 1 bean. Which makes decorators useless :-) -- 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

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-314) Interceptors applied twice on beans when there is a decorator

by Wayne Zhang (JIRA)

Interceptors applied twice on beans when there is a decorator ------------------------------------------------------------- Key: WELD-314 URL: https://jira.jboss.org/jira/browse/WELD-314 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.0.GA Environment: Os: Linux AppServer: Glassfish v3 b73 Reporter: Wayne Zhang Interceptors applied twice when there is a decorator. The following log is from a example application. Bean SimplePaymentService has two interceptors - AuditInterceptor and TransactionInterceptor. Also, SimplePaymentService has a decorator - SecurePaymentService. When business method pay() is called, these 2 interceptors called twice: (Example application in a NetBeans 6.8 project attached) [#|2009-11-24T14:29:03.887+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,885 - INFO weld.lab1.interceptor.TransactionInterceptor - Start transaction for weld.lab1.service.SimplePaymentService_$$_javassist_384, instance=weld.lab1.service.SimplePaymentService@1b5adb0 |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,887 - INFO weld.lab1.interceptor.AuditInterceptor - Method public boolean weld.lab1.service.SimplePaymentService.pay(java.lang.String,java.math.BigDecimal) throws java.lang.Exception on Bean class org.jboss.interceptor.proxy.AbstractClassInterceptionHandler$DelegatingInvocationContext invoked. |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.service.SecurePaymentService - I'm a secure payment service |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.interceptor.TransactionInterceptor - Start transaction for weld.lab1.service.SimplePaymentService_$$_javassist_384, instance=weld.lab1.service.SimplePaymentService@1b5adb0 |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.interceptor.AuditInterceptor - Method public boolean weld.lab1.service.SimplePaymentService.pay(java.lang.String,java.math.BigDecimal) throws java.lang.Exception on Bean class org.jboss.interceptor.proxy.AbstractClassInterceptionHandler$DelegatingInvocationContext invoked. |#] [#|2009-11-24T14:29:03.888+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,888 - INFO weld.lab1.service.SimplePaymentService - Pay $0.03 for NetBeans. |#] [#|2009-11-24T14:29:03.904+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,904 - INFO weld.lab1.event.PaymentServiceListener - Payment processed: account=NetBeans, amount=0.03 |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.interceptor.TransactionInterceptor - Transaction commited. |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.event.PaymentServiceListener - Payment success: account=NetBeans, amount=0.03 |#] [#|2009-11-24T14:29:03.905+0800|INFO|glassfishv3.0|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=26;_ThreadName=Thread-1;|2009-11-24 14:29:03,905 - INFO weld.lab1.interceptor.TransactionInterceptor - Transaction commited. |#] -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-287) Unable to run example in eclipse using m2eclipse as described in documentation

by Martin Gencur (JIRA)

Unable to run example in eclipse using m2eclipse as described in documentation ------------------------------------------------------------------------------ Key: WELD-287 URL: https://jira.jboss.org/jira/browse/WELD-287 Project: Weld Issue Type: Bug Components: Examples Reporter: Martin Gencur Fix For: 1.0.1.CR1 In documentation of weld (bundled with weld), there is a chapter "7.2.1. Creating the Eclipse project" . I was able to import a wicket/numberguess example to eclipse using m2eclipse plugin, but I wasn't able to run the example. When I run src/test/java/org/jboss/weld/examples/wicket/Start.java like Run As -> Java Application, and go to http://localhost:9090/, the following output is displayed: Nov 12, 2009 3:50:34 PM org.apache.wicket.RequestCycle logRuntimeException SEVERE: Can't instantiate page using constructor public org.jboss.weld.examples.wicket.HomePage() org.apache.wicket.WicketRuntimeException: Can't instantiate page using constructor public org.jboss.weld.examples.wicket.HomePage() at org.apache.wicket.session.DefaultPageFactory.createPage(DefaultPageFactory.java:212) at org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:57) at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.newPage(BookmarkablePageRequestTarget.java:299) at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.getPage(BookmarkablePageRequestTarget.java:321) at org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.processEvents(BookmarkablePageRequestTarget.java:234) at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428) at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:289) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:915) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.apache.wicket.session.DefaultPageFactory.createPage(DefaultPageFactory.java:192) ... 26 more Caused by: javax.enterprise.inject.UnsatisfiedResolutionException: class org.jboss.weld.examples.wicket.Game; binding types = [@Default]Unable to resolve any Managed Beans at org.jboss.weld.BeanManagerImpl.getBean(BeanManagerImpl.java:1074) at org.jboss.weld.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:1040) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:727) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:739) at org.jboss.weld.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:115) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:51) at org.jboss.weld.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:109) at org.jboss.weld.wicket.util.NonContextual$Instance.inject(NonContextual.java:121) at org.jboss.weld.wicket.WeldComponentInstantiationListener.onInstantiation(WeldComponentInstantiationListener.java:30) at org.apache.wicket.Application.notifyComponentInstantiationListeners(Application.java:1040) at org.apache.wicket.Component.<init>(Component.java:920) at org.apache.wicket.MarkupContainer.<init>(MarkupContainer.java:113) at org.apache.wicket.MarkupContainer.<init>(MarkupContainer.java:105) at org.apache.wicket.Page.<init>(Page.java:237) at org.apache.wicket.markup.html.WebPage.<init>(WebPage.java:185) at org.jboss.weld.examples.wicket.HomePage.<init>(HomePage.java:23) ... 31 more When I got here: http://localhost:9090/weld-wicket-numberguess , the page displays HTTP ERROR 404 (not found) -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-325) Interceptor method signature validation

by Marius Bogoevici (JIRA)

Interceptor method signature validation --------------------------------------- Key: WELD-325 URL: https://jira.jboss.org/jira/browse/WELD-325 Project: Weld Issue Type: Bug Reporter: Marius Bogoevici Use the fix in JBINTER-5 to make sure that only interceptor method with signatures which are conforming to the JSR-318 rules are actually observed. -- 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

14 years, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2009