July 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDI-3) Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes

by Stuart Douglas (JIRA)

Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes ------------------------------------------------------------------------------------------------------------ Key: CDI-3 URL: https://jira.jboss.org/browse/CDI-3 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Stuart Douglas At the moment AnnotatedTypes can only be added in the BeforeBeanDiscovery phase. This means that if you want to install additional beans based on the beans processed in the ProcessAnnotatedType phase you must instead add implementations of the Bean interface in the AfterBeanDiscovery phase. This interface is more limited than annotated type, and does not let you exactly mimic the behaviour of beans added as AnnotatedTypes. Some of the things that the bean interface will not let you mimic are: - Interceptors - Disposal methods - Producer fields for normal scoped beans -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (CDI-2) Interceptor bindings defined at method level should override those at the class level

by Pete Muir (JIRA)

Interceptor bindings defined at method level should override those at the class level ------------------------------------------------------------------------------------- Key: CDI-2 URL: https://jira.jboss.org/browse/CDI-2 Project: CDI Specification Issues Issue Type: Bug Components: Specification Reporter: Pete Muir We certainly *intended* for method-level interceptor bindings to override bindings declared at the class level, but whether we actually wrote that down is another story. It certainly doesn't look like that behavior is properly defined in the latest version of the spec. In section 9.5.2 of the spec: If the set of interceptor bindings of a bean or interceptor, including bindings inherited from stereotypes and other interceptor bindings, has two instances of a certain interceptor binding type and the instances have different values of some annotation member, the container automatically detects the problem and treats it as a definition error. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (CDITCK-168) extensions.processBean.ProcessBean event count issue

by Scott Ferguson (JIRA)

extensions.processBean.ProcessBean event count issue ---------------------------------------------------- Key: CDITCK-168 URL: https://jira.jboss.org/browse/CDITCK-168 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR1 Environment: any Reporter: Scott Ferguson The issue is in an assertion in extensions.processBean.ProcessBeanTest, counting the number of times the Cowshed bean raises a discovery event. There are three tests affected by this issue: extensions.processBean.ProcessBeanTest testProcessProducerFieldEvent() testProcessProducerMethodEvent() extensions.processBean.ProcessSessionBeanTest testProcessSessionBeanEvent() specifically testProcessProducerMethodEvent() 79: assert ProcessBeanObserver.getCowShedProcessBeanCount() == 2; testProcessProducerFieldEvent() 102: assert ProcessBeanObserver.getChickenHutchProcessBeanCount() == 2; testProcessSessionBeanEvent() 63: assert ProcessBeanObserver.getElephantProcessBeanCount() == 2; But I can't see how this number is 2 instead of 1. The Cowshed looks like: public class Cowshed { @Produces public Cow getDaisy() { ... } } So there should be 3 relevant extension events fired: ProcessBean<Cowshed> ProcessProducerMethod<Cowshed, Cow> ProcessBean<Cow> I double checked the ProcessProducerMethod interface: ProcessProducerMethod<T,X> extends ProcessBean<X> which is where the ProcessBean<Cow> comes from, but I don't see where the 2nd ProcessBean<Cowshed> comes from. The ProcessSessionBean issue is essentially the same -- 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

15 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (WELDX-80) Exception thrown by GAE local ode

by Pete Muir (JIRA)

Exception thrown by GAE local ode --------------------------------- Key: WELDX-80 URL: https://jira.jboss.org/jira/browse/WELDX-80 Project: Weld Extensions Issue Type: Bug Components: Servlet Containers Reporter: Pete Muir Feb 21, 2010 11:06:12 PM com.google.appengine.tools.development.JettyContainerService$ScannerListener fileChanged INFO: /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/appengine-web.xml updated, reloading the webapp! Feb 21, 2010 11:06:12 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml INFO: Successfully processed /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/appengine-web.xml Feb 21, 2010 11:06:12 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml INFO: Successfully processed /Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp/WEB-INF/web.xml Bad level value for property: .level Feb 21, 2010 11:06:13 PM org.jboss.weld.bootstrap.WeldBootstrap <clinit> INFO: WELD-000900 1.0.1 (Final) Feb 21, 2010 11:06:13 PM org.jboss.weld.bootstrap.WeldBootstrap startContainer INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously. Feb 21, 2010 11:06:13 PM org.jboss.weld.environment.servlet.Listener contextInitialized INFO: JSR-299 injection will not be available in Servlets, Filters etc. This facility is only available in Tomcat Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: failed com.google.apphosting.utils.jetty.DevAppEngineWebAppContext(a)36101d01{/,/Users/pmuir/workspace/weld-build/dist/weld-1.0.1-Final/examples/jsf/numberguess/src/main/webapp} java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext; at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305) at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250) at org.mortbay.util.Scanner.reportChange(Scanner.java:434) at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305) at org.mortbay.util.Scanner.scan(Scanner.java:254) at org.mortbay.util.Scanner$1.run(Scanner.java:225) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: failed JettyContainerService$ApiProxyHandler@56dc64a2 java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext; at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305) at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250) at org.mortbay.util.Scanner.reportChange(Scanner.java:434) at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305) at org.mortbay.util.Scanner.scan(Scanner.java:254) at org.mortbay.util.Scanner$1.run(Scanner.java:225) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Feb 21, 2010 11:06:13 PM com.google.apphosting.utils.jetty.JettyLogger warn WARNING: EXCEPTION java.lang.AbstractMethodError: javax.servlet.jsp.JspFactory.getJspApplicationContext(Ljavax/servlet/ServletContext;)Ljavax/servlet/jsp/JspApplicationContext; at org.jboss.weld.environment.servlet.Listener.contextInitialized(Listener.java:157) at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:530) at org.mortbay.jetty.servlet.Context.startContext(Context.java:135) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1218) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:500) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:117) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40) at com.google.appengine.tools.development.JettyContainerService.reloadWebApp(JettyContainerService.java:305) at com.google.appengine.tools.development.JettyContainerService$ScannerListener.fileChanged(JettyContainerService.java:250) at org.mortbay.util.Scanner.reportChange(Scanner.java:434) at org.mortbay.util.Scanner.reportDifferences(Scanner.java:305) at org.mortbay.util.Scanner.scan(Scanner.java:254) at org.mortbay.util.Scanner$1.run(Scanner.java:225) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) -- 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

[JBoss JIRA] Created: (WELD-522) Weld makes my Java SE app startup time >100x slower

by Morten Christensen (JIRA)

Weld makes my Java SE app startup time >100x slower ---------------------------------------------------- Key: WELD-522 URL: https://jira.jboss.org/jira/browse/WELD-522 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Java 6, Weld 1.01 SE + lots of jars on the classpath Reporter: Morten Christensen Booting my Java SE app without weld takes << 1s BUT the 1 line for initializing weld to autowire my app takes at least 4-5 seconds. My app is not so big and consist of ~20-30 singletons that must be wired + various other non-weld stuff. I have lots of stuff on my classpath so I suspect that could be why weld is going crazy. I guess this could be improved if I can have weld limited to work only inside my own jar and/or only work with specific classes/packages. P.S. With breakpoints enabled in a debugger and a bit of unluck, I was even able to have welds initialization to take ~ 5 minutes one day (reduced to seconds again after I removed all breakpoints though). -- 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

3
14
0 / 0

[JBoss JIRA] Created: (WELD-405) Add manual verification process for GAE support to QA guide

by Pete Muir (JIRA)

Add manual verification process for GAE support to QA guide ----------------------------------------------------------- Key: WELD-405 URL: https://jira.jboss.org/jira/browse/WELD-405 Project: Weld Issue Type: Feature Request Components: Class Beans (Managed and Session) Reporter: Pete Muir Assignee: Shane Bryzak Fix For: 1.0.1.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

15 years, 3 months

1
11
0 / 0

[JBoss JIRA] Created: (WELD-211) Tests which exercise an SPI implementation

by Pete Muir (JIRA)

Tests which exercise an SPI implementation ------------------------------------------ Key: WELD-211 URL: https://jira.jboss.org/jira/browse/WELD-211 Project: Weld Issue Type: Feature Request Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Pete Muir Fix For: 1.0.1.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

15 years, 3 months

1
5
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

15 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (CDITCK-137) org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest ------------------------------------------------------------------------------------------------------- Key: CDITCK-137 URL: https://jira.jboss.org/jira/browse/CDITCK-137 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Method : testChainedDecoratorInvocation In this test, TCK tests the injection points of the Decortor delegate. But it seems that this test is specific to Weld. In our case, we manage decorator stack via single delegate not via injection each decorator reference to DecoratorInvocationTest -- 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, 4 months

3
22
0 / 0

[JBoss JIRA] Created: (CDITCK-138) org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.lookup.injectionpoint.InjectionPointTest ------------------------------------------------------------------- Key: CDITCK-138 URL: https://jira.jboss.org/jira/browse/CDITCK-138 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu In the testIsDelegateMethod(), assert cat.getInjectionPoint().isDelegate(); But Cat injection point is not decorator delegate point. -- 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, 4 months

3
16
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2010