August 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-542) Exception messages missing useful information: "Injection point has unsatisfied/ambiguous dependencies

by Lincoln Baxter III (JIRA)

Exception messages missing useful information: "Injection point has unsatisfied/ambiguous dependencies ------------------------------------------------------------------------------------------------------ Key: WELD-542 URL: https://jira.jboss.org/browse/WELD-542 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.0.1.Final Reporter: Lincoln Baxter III I feel like the following exception message is missing some very useful information (e.g, the type of the object that could not be satisfied;) I don't want to have to look at the injection point in order to see what it couldn't find. Also, I have to skim over a few words before I get the information that really tells me what's going on. "Unsatisfied dependencies" should be the primary focus of the message. WELD-001408 Injection point has unsatisfied dependencies. Injection point: field org.jboss.seam.faces.status.MessagesAdapter.context; Qualifiers: [@javax.enterprise.inject.Default()] The message should probably look something like this, instead: WELD-001408 Unsatisfied dependencies for type [org.jboss.seam.international.status.Messages] at injection point [field] [org.jboss.seam.faces.status.MessagesAdapter.context]. Qualifiers: [@javax.enterprise.inject.Default()] This way, I immediately know that I have unsatisfied dependencies, and the type that cannot be resolved. From there, I can see where the type is being requested and its qualifiers. I'd like to see the same thing done for the Ambiguous dependencies exception message: Existing: Injection point has ambiguous dependencies. Injection point: field org.jboss.seam.faces.status.MessagesAdapter.context; Qualifiers: [@javax.enterprise.inject.Default()]; Possible dependencies: [org.jboss.seam.international.status.Messages1, org.jboss.seam.international.status.Messages2] Proposed: Ambiguous dependencies for type [org.jboss.seam.international.status.Messages] at injection point [field] [org.jboss.seam.faces.status.MessagesAdapter.context]. Qualifiers: [@javax.enterprise.inject.Default()]; Possible dependencies: [org.jboss.seam.international.status.Messages1, org.jboss.seam.international.status.Messages2] -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-124) Allow generic producers to be a scope other than @Dependent

by Pete Muir (JIRA)

Allow generic producers to be a scope other than @Dependent ----------------------------------------------------------- Key: WELDX-124 URL: https://jira.jboss.org/browse/WELDX-124 Project: Weld Extensions Issue Type: Feature Request Reporter: Pete Muir Fix For: 1.0.0.Alpha3 -- 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

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (WELDX-87) weldContainer.instance().select().iterator() contains null element

by Samuli Saarinen (JIRA)

weldContainer.instance().select().iterator() contains null element ------------------------------------------------------------------ Key: WELDX-87 URL: https://jira.jboss.org/jira/browse/WELDX-87 Project: Weld Extensions Issue Type: Bug Components: Java SE Environment: Java 1.6, weld-se.1.0.1-Final Reporter: Samuli Saarinen {code} private Weld weld; private WeldContainer container; @BeforeMethod public void beforeMethod() throws Exception { weld = new Weld(); container = weld.initialize(); } @Test public void testSelect() throws Exception { Iterator<Object> iter = container.instance().select().iterator(); while (iter.hasNext()) { assertNotNull(iter.next()); } } @AfterMethod public void afterMethod() { weld.shutdown(); } {code} -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-572) Process event implementations do casts without checking for null first

by Pete Muir (JIRA)

Process event implementations do casts without checking for null first ---------------------------------------------------------------------- Key: WELD-572 URL: https://jira.jboss.org/browse/WELD-572 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir Priority: Critical Fix For: 1.1.0.BETA1 -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-557) InjectionTarget methods called with a proxied instance

by Jozef Hartinger (JIRA)

InjectionTarget methods called with a proxied instance ------------------------------------------------------ Key: WELD-557 URL: https://jira.jboss.org/browse/WELD-557 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Jozef Hartinger Priority: Critical Fix For: 1.0.2.CR1 Let's have a bean whose InjectionTarget is wrapped by an extension to provide additional dependency injection, etc... Although it is not explicitly stated in the spec, it is obvious that inject(), postConstruct() and preDestroy() methods of the InjectionTarget should be called with the actual raw bean instance and not with a client proxy. org.jboss.weld.tests.extensions.injectionTarget.InjectionTargetTest (Consider moving the test into the TCK if the presumtion can be implied) -- 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

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (WELD-569) Change proxy CL to TCCL

by David Allen (JIRA)

Change proxy CL to TCCL ----------------------- Key: WELD-569 URL: https://jira.jboss.org/browse/WELD-569 Project: Weld Issue Type: Bug Components: Class Beans (Managed and Session) Reporter: David Allen Assignee: David Allen Priority: Critical Fix For: 1.1.0.BETA1 The class loader used to create proxies should be changed from the base class' CL to the thread context class loader in the default proxy services, SimpleProxyServices. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-552) CDI-API is leaking TestNG to everyone

by Aslak Knutsen (JIRA)

CDI-API is leaking TestNG to everyone ------------------------------------- Key: WELD-552 URL: https://jira.jboss.org/browse/WELD-552 Project: Weld Issue Type: Bug Components: CDI API Reporter: Aslak Knutsen Assignee: Aslak Knutsen CDI-API now has a TestCase, but the TestNG dependency is set to default(compile) which means anyone depending on CDI-API will be forced to use TestNG. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-562) Thread safety issues in ContextualStoreImpl

by Stuart Douglas (JIRA)

Thread safety issues in ContextualStoreImpl -------------------------------------------- Key: WELD-562 URL: https://jira.jboss.org/browse/WELD-562 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Priority: Minor Fix For: 1.1.0.BETA1 -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-546) Beans producing stuff have their proxies proxying the product

by Nicklas Karlsson (JIRA)

Beans producing stuff have their proxies proxying the product ------------------------------------------------------------- Key: WELD-546 URL: https://jira.jboss.org/browse/WELD-546 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Assignee: David Allen Given @Model public class GreetingBean { @Produces @Model Greeting greeting = new Greeting(); public void ping() { } } #{greetingBean.ping} gives an "Method not found" exception because the GreetingBean_$$_WeldProxy is actually proxing Greeting -- 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

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (WELD-564) Migrate to Google Guava from google-collections

by Nick Belaevski (JIRA)

Migrate to Google Guava from google-collections ----------------------------------------------- Key: WELD-564 URL: https://jira.jboss.org/browse/WELD-564 Project: Weld Issue Type: Feature Request Components: Infrastructure Environment: JBoss 6.0.0-SNAPSHOT (pre-M4) Reporter: Nick Belaevski weld-deployer comes with google-collections library and that seems to be causing problems for projects using guava (that is the later version of collections library + foundation classes). Please see related forum thread also. -- 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

14 years, 4 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2010