August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-621) Write tutorial for pastecode for refguide

by Pete Muir (JIRA)

Write tutorial for pastecode for refguide ----------------------------------------- Key: WELD-621 URL: https://jira.jboss.org/browse/WELD-621 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Assignee: Dan Allen -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (WELDX-74) Support use of decorator of Callable<T>

by Elias Ross (JIRA)

Support use of decorator of Callable<T> --------------------------------------- Key: WELDX-74 URL: https://jira.jboss.org/jira/browse/WELDX-74 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Elias Ross Decorator exists for Runnable. Should allow for Callable<T> to be used as well. This is actually pretty useful, for example if you want to execute under a temporary new scope in the same thread, e.g. @Inject Instance<PaymentProcessor> paymentProcessorSource; // which implements Callable<Result> Result result = paymentProcessorSource.get().call(); Or, in the case of a thread pool, you can use Future<T> etc. /** * Decorator for all beans which implements Callable. It intercepts the call * to the call() method to set up the ThreadContext for the new thread so that * instances of @ThreadScoped beans can be correctly resolved. */ @Decorator public class CallableDecorator<T> implements Callable<T> { @Inject @Delegate Callable<T> callable; /** * Set up the ThreadContet and delegate. */ public T call() { // set up context for this thread final ThreadContext threadContext = WeldSEBeanRegistrant.THREAD_CONTEXT; threadContext.setBeanStore(new HashMapBeanStore()); threadContext.setActive(true); // run the original thread try { return callable.call(); } finally { threadContext.destroy(); } } -- 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

12 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (WELD-439) conversation example

by Dan Allen (JIRA)

conversation example -------------------- Key: WELD-439 URL: https://jira.jboss.org/jira/browse/WELD-439 Project: Weld Issue Type: Feature Request Components: Examples Affects Versions: 1.0.1.CR2 Reporter: Dan Allen There should be an example that demonstrates the minimal use of conversations, perhaps using the example from the spec or reference guide. The example should include a scenario where the conversation is propagated on a postback, both with and without <f:ajax>. -- 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

12 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (WELD-494) Add Arquillian test to the dist examples

by Aslak Knutsen (JIRA)

Add Arquillian test to the dist examples ---------------------------------------- Key: WELD-494 URL: https://jira.jboss.org/jira/browse/WELD-494 Project: Weld Issue Type: Task Components: Examples Reporter: Aslak Knutsen The Weld/CDI examples that are included in the Weld dist should come complete with Arquillian test suites showing how to test. Both embedded/container. -- 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

12 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-498) A better way to specify the version than using the manifest

by Pete Muir (JIRA)

A better way to specify the version than using the manifest ----------------------------------------------------------- Key: WELD-498 URL: https://jira.jboss.org/jira/browse/WELD-498 Project: Weld Issue Type: Feature Request Components: Infrastructure Reporter: Pete Muir This is flaky as the manifest gets rewritten. Steve Ebersole did something where he wrote it to a class as part of the build -- 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

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-38) ConversationScoped not working on Tomcat

by Fabio Wang (JIRA)

ConversationScoped not working on Tomcat ---------------------------------------- Key: WELDX-38 URL: https://jira.jboss.org/jira/browse/WELDX-38 Project: Weld Extensions Issue Type: Bug Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR1 Environment: Apache Tomcat 6.0.20 Reporter: Fabio Wang Trying to mark a conversation as long-running causes an exception (java.lang.NoClassDefFoundError: javassist/util/proxy/ProxyObject) when the ServletConversationManager tries to get a proxy for the httpSession. The ProxyFactory.classLoaderProvider ends up resolving the classloader to an instance of org.apache.catalina.loader.StandardClassLoader (which doesn't know the javassist lib, since it's only in the app classloader). -- 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

12 years, 10 months

5
24
0 / 0

[JBoss JIRA] Created: (WELD-446) Improve startup times

by Shane Bryzak (JIRA)

Improve startup times --------------------- Key: WELD-446 URL: https://jira.jboss.org/jira/browse/WELD-446 Project: Weld Issue Type: Task Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.CR2 Reporter: Shane Bryzak Assignee: Pete Muir We need to improve startup times for environments such as Google App Engine, which are currently in the range of 4-6 seconds. -- 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

12 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (WELD-627) Clarify the implementation and usage of WeldClass.getWeldMethods, WelldClass.getDeclaredWeldMethods

by Marius Bogoevici (JIRA)

Clarify the implementation and usage of WeldClass.getWeldMethods, WelldClass.getDeclaredWeldMethods --------------------------------------------------------------------------------------------------- Key: WELD-627 URL: https://jira.jboss.org/browse/WELD-627 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Marius Bogoevici Fix For: 1.1.0.BETA2 The goal for getWeldMethods and getDeclaredWeldMethods is to mimic the behavior of getMethods and getDeclaredMethods as they are defined on java.lang.Class. Introduce a new method - called e.g. getWeldBusinessMethods that returns the methods of the class that can be used for business methods invocations on a particular bean. -- 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

12 years, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (WELD-516) RunnableDecorator incorrectly assumes >0 Runnable beans

by Morten Christensen (JIRA)

RunnableDecorator incorrectly assumes >0 Runnable beans ------------------------------------------------------- Key: WELD-516 URL: https://jira.jboss.org/jira/browse/WELD-516 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: Java 6 + WeldSE Reporter: Morten Christensen The class org.jboss.weld.environment.se.threading.RunnableDecorator incorrectly assumes that there will be at least one bean that implements Runnable. If there are no beans that implements Runnable then an error like this will happen: org.jboss.weld.DeploymentException: Injection point has unstatisfied dependencies. Injection point: field org.jboss.weld.environment.se.threading.RunnableDecorator.runnable; Qualifiers: [@javax.enterprise.inject.Default()] at org.jboss.weld.Validator.validateInjectionPoint(Validator.java:232) at org.jboss.weld.Validator.validateBean(Validator.java:80) at org.jboss.weld.Validator.validateRIBean(Validator.java:100) at org.jboss.weld.Validator.validateBeans(Validator.java:282) at org.jboss.weld.Validator.validateDeployment(Validator.java:267) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:389) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:81) at org.jboss.weld.environment.se.StartMain.go(StartMain.java:45) at org.jboss.weld.environment.se.StartMain.main(StartMain.java:57) I guess the field "runnable" inside this class should be changed to use Instance<Runnable> instead. -- 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

12 years, 10 months

6
12
0 / 0

[JBoss JIRA] Created: (CDITCK-63) Test decorators and interceptors in other scopes than @Dependent

by Marius Bogoevici (JIRA)

Test decorators and interceptors in other scopes than @Dependent ---------------------------------------------------------------- Key: CDITCK-63 URL: https://jira.jboss.org/jira/browse/CDITCK-63 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Marius Bogoevici Prompted by https://jira.jboss.org/jira/browse/WELD-296 (at the time when the issue was reported decorators were not working correctly with client proxies). This is an implied assertion, but due to the complexity of the implementation, it is still desirable to see that the implementation handles it correctly. -- 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

12 years, 11 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010