April 2009 - weld-issues - Jboss List Archives

[webbeans-issues] [JBoss JIRA] Created: (WBRI-216) Export web beans core unit test infrastructure somehow

by Pete Muir (JIRA)

Export web beans core unit test infrastructure somehow ------------------------------------------------------ Key: WBRI-216 URL: https://jira.jboss.org/jira/browse/WBRI-216 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Priority: Critical 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, 7 months

1
1
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-219) Use SNAPSHOT policy never for all SNAPSHOT dependencies

by Sahoo Sahoo (JIRA)

Use SNAPSHOT policy never for all SNAPSHOT dependencies ------------------------------------------------------- Key: WBRI-219 URL: https://jira.jboss.org/jira/browse/WBRI-219 Project: Web Beans Issue Type: Bug Environment: generic Reporter: Sahoo Sahoo Current pom.xmls in webbeans/ri/trunk have quite a few SNAPSHOT dependency. e.g., jsr299-tck-impl. Imagine a developer doing this: day 1: svn up, mvn clean install // This refreshed maven-repo-local with a new copy of jsr299-tck-impl day 2: mvn install // This again brings a newer copy of jsr299-tck-impl. Who guarantees that the latest copy of jsr299-tck-impl is compatible with svn rev corresponding to previous day? Nobody. So, I suggest the SNAPSHOT update policy be set to NEVER so that user can run mvn -U when they refresh the workspace. -- 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, 7 months

2
4
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-222) dynamic lookup ParameterizedType

by Takeshi Kondo (JIRA)

dynamic lookup ParameterizedType -------------------------------- Key: WBRI-222 URL: https://jira.jboss.org/jira/browse/WBRI-222 Project: Web Beans Issue Type: Bug Components: Producer beans Affects Versions: 1.0.0.BETA1 Reporter: Takeshi Kondo for instance, @Obtains Instance<List<String>> instance; - This code causes exception, because InstanceBean don't deal with ParameterizedType. -- 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, 7 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-223) getting javax.inject.Instance from Manager#getInstanceByType causes NullPointerException

by Takeshi Kondo (JIRA)

getting javax.inject.Instance from Manager#getInstanceByType causes NullPointerException ---------------------------------------------------------------------------------------- Key: WBRI-223 URL: https://jira.jboss.org/jira/browse/WBRI-223 Project: Web Beans Issue Type: Bug Reporter: Takeshi Kondo Because ManagerImpl#getInjectionPoint() is null in AbstractFacadeBean#create, following sample code throws NullPointerException. -- sample code --- Instance<List> instance = manager.getInstanceByType(new TypeLiteral<Instance<List>>(){}, new ObtainsLiteral()); -- 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, 7 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-161) Support child activities

by Pete Muir (JIRA)

Support child activities ------------------------ Key: WBRI-161 URL: https://jira.jboss.org/jira/browse/WBRI-161 Project: Web Beans Issue Type: Feature Request Reporter: Pete Muir -- 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, 7 months

1
4
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-221) @ThreadScoped in SE

by Peter Royle (JIRA)

@ThreadScoped in SE ------------------- Key: WBRI-221 URL: https://jira.jboss.org/jira/browse/WBRI-221 Project: Web Beans Issue Type: Feature Request Environment: Java SE w/o EJB Reporter: Peter Royle Priority: Minor Create a @ThreadScoped annotation and ThreadContext which is simply backed by ThreadLocal. This enables: @ThreadScoped String str = "hello"; to replace ThreadLocal<String> strTL = new ThreadLocal<String>(); strTL.set("hello"; -- 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, 7 months

2
2
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-220) Manual Shutdown i nSE by Configuration

by Peter Royle (JIRA)

Manual Shutdown i nSE by Configuration -------------------------------------- Key: WBRI-220 URL: https://jira.jboss.org/jira/browse/WBRI-220 Project: Web Beans Issue Type: Feature Request Environment: Java SE, w/o EJB Reporter: Peter Royle Priority: Minor The developer could set a configuration variable to let WebBeans know that they will be taking responsibility for initiating the shutdown sequence when it makes sense for their app, and hence WebBeans needn't do any automatic shutdown sequence. This could be done programatically: public void (@Observes Deployed Manager manager, @Parameters List<String> params, @Current Configuration config) { config.setManualShutdown(true); System.out.println("You provided " + params.size() + " parameters. Well done."); } Alternatively this could be done by setting a property in beans.xml or beans.properties. -- 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, 7 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-218) Webbeans breaks jsf Message Bundle

by Martin Eigenbrodt (JIRA)

Webbeans breaks jsf Message Bundle ---------------------------------- Key: WBRI-218 URL: https://jira.jboss.org/jira/browse/WBRI-218 Project: Web Beans Issue Type: Bug Reporter: Martin Eigenbrodt This problem seems to be introduced by the fix for WBRI-174 / Commit 2060. I've got A JSF page that load a resource bundle: <f:loadBundle var="msg" basename="de.my.basename" /> and later uses the values: .. #{msg.label_velocity} .. This worked fine with an older Snapshot of WebBeans but since I updated to the current version I only getStrings like: Namespace(msg.label_velocity.) -- 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, 7 months

2
3
0 / 0

[webbeans-issues] [JBoss JIRA] Created: (WBRI-215) Manager.getInstanceToInject() does not throw an UnproxyableDependencyException for unproxyable bean types

by Shane Bryzak (JIRA)

Manager.getInstanceToInject() does not throw an UnproxyableDependencyException for unproxyable bean types --------------------------------------------------------------------------------------------------------- Key: WBRI-215 URL: https://jira.jboss.org/jira/browse/WBRI-215 Project: Web Beans Issue Type: Bug Affects Versions: 1.0.0.BETA1 Reporter: Shane Bryzak The spec states in section 5.7.1: "Manager.getInstanceToInject() returns a contextual instance or client proxy to be injected to the given injection point. The getInstanceToInject() method must: <snip> * If the bean has a normal scope and the type cannot be proxied by the container, as defined in Section 5.4.1, "Unproxyable bean types", throw an UnproxyableDependencyException." This exception is not being thrown for unproxyable bean types - see TCK test org.jboss.jsr299.tck.tests.lookup.dependency.resolution.DependencyResolutionTest, method testGetInstanceToInjectThrowsUnproxyableDependencyException(). Section 5.4.1 of the spec lists "classes without a non-private constructor with no parameters" as an unproxyable bean type. -- 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, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2009