December 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-997) Custom implementation of Interceptor never invokedi

by Jozef Hartinger (Created) (JIRA)

Custom implementation of Interceptor never invokedi --------------------------------------------------- Key: WELD-997 URL: https://issues.jboss.org/browse/WELD-997 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

8
9
0 / 0

[JBoss JIRA] Created: (WELD-731) Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)

by Dan Allen (JIRA)

Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5) --------------------------------------------------------------------------------- Key: WELD-731 URL: https://jira.jboss.org/browse/WELD-731 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Fix For: 1.1.0.CR1 It's possible for the Weld servlet listener to be proactive and bind the BeanManager to JNDI when the naming context is read/write, as it is in JBoss AS and EAP 5. There's another good reason why this needs to be done. JBoss AS does not support defining naming resources in context.xml (which on JBoss AS is WEB-INF/context.xml). Therefore, there's no other way to push the BeanManager into JNDI. The logic for this feature is pretty straightforward. Look for the BeanManager in JNDI. If it's not there, attempt to put it there. If that fails, just log a warning message that the BeanManager will not be available in JNDI. -- 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, 9 months

7
11
0 / 0

[JBoss JIRA] Created: (WELD-413) It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType

by Stuart Douglas (JIRA)

It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType -------------------------------------------------------------------------------------- Key: WELD-413 URL: https://jira.jboss.org/jira/browse/WELD-413 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.CR1 Reporter: Stuart Douglas Priority: Minor Adding a bean that is exactly the same as an existing bean results in the added bean being ignored. I can't think of a use case for having two beans exactly the same, however it still should work, and may be a symptom of a larger problem. -- 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, 9 months

4
8
0 / 0

[JBoss JIRA] (WELD-999) Interceptor binding transitivity broken

by Jozef Hartinger (Created) (JIRA)

Interceptor binding transitivity broken --------------------------------------- Key: WELD-999 URL: https://issues.jboss.org/browse/WELD-999 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1 See org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
8
0 / 0

[JBoss JIRA] (WELD-989) #{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide

by Marek Schmidt (Created) (JIRA)

#{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide ---------------------------------------------------------------------------------------------------------- Key: WELD-989 URL: https://issues.jboss.org/browse/WELD-989 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.2.Final Reporter: Marek Schmidt http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.htm... on the line "<a href="/addProduct.jsp?cid=#{conversation.id}">Add Product</a>" and in the sentence "The unique identifier of the conversation may be obtained from the Conversation object, which has the EL bean name conversation. " -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (WELD-926) Weld Servlet still uses old Google Collections instead of Guava

by Sebastian Schaffert (JIRA)

Weld Servlet still uses old Google Collections instead of Guava --------------------------------------------------------------- Key: WELD-926 URL: https://issues.jboss.org/browse/WELD-926 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Sebastian Schaffert Even though WELD-564 is fixed, the latest version of Weld Servlet still includes the old Google Collections code. I think it should not contain the code at all and instead use a dependency on the library. Or at least update to the latest version of Guava. The problem is that it makes it impossible to use Guava in the same classpath as Weld. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (WELD-894) Around-Invoke interceptors should not wrap RuntimeException into WeldException

by Vlastimil Menčík (JIRA)

Around-Invoke interceptors should not wrap RuntimeException into WeldException ------------------------------------------------------------------------------ Key: WELD-894 URL: https://issues.jboss.org/browse/WELD-894 Project: Weld Issue Type: Feature Request Components: Interceptors and Decorators Affects Versions: 1.1.1.Final Reporter: Vlastimil Menčík Currently, org.jboss.weld.bean.InterceptorImpl always throws a WeldException when the invoked method throws an exception. This causes all exceptions in intercepted session bean methods to be treated as system exceptions by the EJB subsystem as WeldException is a system exception. If RuntimeExceptions were simply rethrown, such exceptions (annotated with javax.ejb.ApplicationException) could pass through the interceptor unwrapped and be recognized as application exception in the EJB sense. Of course, checked application exceptions are a bigger problem that would probably require a more sofisticated solution, that could be resolved later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

4
4
0 / 0

[JBoss JIRA] (WELD-1000) Pass extension instances to bootstrap

by Pete Muir (Created) (JIRA)

Pass extension instances to bootstrap ------------------------------------- Key: WELD-1000 URL: https://issues.jboss.org/browse/WELD-1000 Project: Weld Issue Type: Feature Request Components: Java SE Support Affects Versions: 1.1.2.Final Reporter: Pete Muir If you are bootstrapping Weld yourself using new Weld() it would be nice to be able to pass in an already created Extension instance, rather than have the container instantiate it from META-INF/services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-954) URIs escaped twice in URLScanner

by Emond Papegaaij (JIRA)

URIs escaped twice in URLScanner -------------------------------- Key: WELD-954 URL: https://issues.jboss.org/browse/WELD-954 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 1.1.2.Final Reporter: Emond Papegaaij The fix for WELD-834 can cause spaces to be escaped twice in an URL. This leads to errors like: Error handling file /var/lib/jenkins/jobs/Wicket%2520Weld/workspace/wicket-cdi-examples/target/classes Notice how 'Wicket%20Weld' is escaped to 'Wicket%2520Weld'. https://github.com/papegaaij/wicket-cdi demonstrates the problem, clone the project in a directory with a space in the name, and run 'mvn install -Dwicket.version=1.5-RC5.1'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

7
9
0 / 0

[JBoss JIRA] Created: (WELD-937) Documentation issue - Instantiating abstract class

by Sebastian Wramba (JIRA)

Documentation issue - Instantiating abstract class -------------------------------------------------- Key: WELD-937 URL: https://issues.jboss.org/browse/WELD-937 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.1.0.Final Reporter: Sebastian Wramba In chapter 4.10 the abstract class AsynchronousQualifier is defined. The next code sample instantiates this AsynchronousQualifier. However, instantiating an abstract class is not allowed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2011