April 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-496) Examples named incorrectly in the Weld reference documentation

by asookazian (JIRA)

Examples named incorrectly in the Weld reference documentation -------------------------------------------------------------- Key: WELD-496 URL: https://jira.jboss.org/jira/browse/WELD-496 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Environment: N/A Reporter: asookazian Priority: Trivial The following needs attention: "Weld comes with two starter example applications, in addition to more specialized examples. The first, weldnumberguess, is a web (war) example containing only non-transactional managed beans. This example can be run on a wide range of servers, including JBoss AS, GlassFish, Apache Tomcat, Jetty, Google App Engine, and any compliant Java EE 6 container. The second example, weld-translator, is an enterprise (ear) example that contains session beans. This example must be run on JBoss AS 6.0, Glassfish 3.0 or any compliant Java EE 6 container." There are many more start example apps now in 1.0.1. Also, the names of the two cited above have changed to numberguess and translator. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-484) Static observer methods should not go through bean resolution

by David Allen (JIRA)

Static observer methods should not go through bean resolution ------------------------------------------------------------- Key: WELD-484 URL: https://jira.jboss.org/jira/browse/WELD-484 Project: Weld Issue Type: Bug Reporter: David Allen Assignee: David Allen Fix For: 1.0.2.CR1 org.jboss.jsr299.tck.tests.event.testStaticObserverMethodInvoked -- 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

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-486) Ambiguous dependency when using a decorator

by Ramon Rockx (JIRA)

Ambiguous dependency when using a decorator ------------------------------------------- Key: WELD-486 URL: https://jira.jboss.org/jira/browse/WELD-486 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.CR1 Environment: Glassfish v3.0.1 b12 (Windows) Reporter: Ramon Rockx If an decorated interface is implemented more than once and the interface {{extends Serializable}} the deployment will fail with a {{WELD-001318 Cannot resolve an ambiguous dependency between <all implementations>}} message. See http://www.seamframework.org/Community/SerializableDecorators for an example. I will try to attach a complete example later. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-492) Allow servlet listeners to be managed beans

by Nicklas Karlsson (JIRA)

Allow servlet listeners to be managed beans ------------------------------------------- Key: WELD-492 URL: https://jira.jboss.org/jira/browse/WELD-492 Project: Weld Issue Type: Bug Components: Activities Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Fix For: 1.0.2.CR1 Loosen then check return !Extension.class.isAssignableFrom(clazz.getJavaClass()) && !(clazz.isAnonymousClass() || (clazz.isMemberClass() && !clazz.isStatic())) && !Reflections.isParamerterizedTypeWithWildcard(javaClass) && !servletApiAbstraction.SERVLET_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.FILTER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.SERVLET_CONTEXT_LISTENER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.HTTP_SESSION_LISTENER_CLASS.isAssignableFrom(javaClass) && !servletApiAbstraction.SERVLET_REQUEST_LISTENER_CLASS.isAssignableFrom(javaClass) && !ejbApiAbstraction.ENTERPRISE_BEAN_CLASS.isAssignableFrom(javaClass) && !jsfApiAbstraction.UICOMPONENT_CLASS.isAssignableFrom(javaClass) && (hasSimpleWebBeanConstructor(clazz) || InstantiatorFactory.useInstantiators()); in AbstractBeanDeployer to only prohibit classes explicitly mentioned in the spec, allowing servlet listeners to be managed beans (and UIComponents, too?) -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (WELD-459) A final class interceptor or an interceptor class with a final method not detected as a definition error

by Ondrej Skutka (JIRA)

A final class interceptor or an interceptor class with a final method not detected as a definition error -------------------------------------------------------------------------------------------------------- Key: WELD-459 URL: https://jira.jboss.org/jira/browse/WELD-459 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: If the bean class of a managed bean declares or inherits a class level interceptor binding or a stereotype with interceptor bindings, it must not be declared final, or have any non-static, non-private, final methods. If a managed bean has a class- level interceptor binding and is declared final or has a non-static, non-private, final method, the container automatically detects the problem and treats it as a definition error. If a non-static, non-private method of a bean class of a managed bean declares a method level interceptor binding, neither the method nor the bean class may be declared final. If a non-static, non-private, final method of a managed bean has a method level interceptor binding, the container automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalClassMethodLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodClassLevelInterceptorTest org.jboss.jsr299.tck.tests.interceptors.definition.broken.finalClassInterceptor.FinalMethodMethodLevelInterceptorTest In the TCK trunk -- 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

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (WELD-503) Weld is firing Process*Bean for all beans, not just enabled beans

by Pete Muir (JIRA)

Weld is firing Process*Bean for all beans, not just enabled beans ----------------------------------------------------------------- Key: WELD-503 URL: https://jira.jboss.org/jira/browse/WELD-503 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Reporter: Pete Muir 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (WELDX-77) Weld SE Numberguess is not running from the IDE

by Pete Muir (JIRA)

Weld SE Numberguess is not running from the IDE ----------------------------------------------- Key: WELDX-77 URL: https://jira.jboss.org/jira/browse/WELDX-77 Project: Weld Extensions Issue Type: Task Components: Java SE Reporter: Pete Muir Assignee: Peter Royle Fix For: Java SE 1.0.0.CR3 Or possibly more detailed instructions are needed. -- 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

13 years, 10 months

2
12
0 / 0

[JBoss JIRA] Created: (WELDX-49) error during shutdown on Jetty: no class org.apache.AnnotationProcessor

by Dan Allen (JIRA)

error during shutdown on Jetty: no class org.apache.AnnotationProcessor ----------------------------------------------------------------------- Key: WELDX-49 URL: https://jira.jboss.org/jira/browse/WELDX-49 Project: Weld Extensions Issue Type: Bug Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR2 Reporter: Dan Allen Assignee: Dan Allen Fix For: Servlet Containers 1.0.0.CR3 Exception in thread "Shutdown" java.lang.NoClassDefFoundError: org/apache/AnnotationProcessor ... at org.jboss.weld.environment.servlet.Listener.contextDestroyed(Listener.java:81) Because of this line: sce.getServletContext().removeAttribute(WeldAnnotationProcessor.class.getName()); Need to check for class being available. -- 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

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (WELDX-48) Revisit the way we bind BeanManager to JNDI in Tomcat.

by Pete Muir (JIRA)

Revisit the way we bind BeanManager to JNDI in Tomcat. ------------------------------------------------------ Key: WELDX-48 URL: https://jira.jboss.org/jira/browse/WELDX-48 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Reporter: Pete Muir Currently we rely on the deprecated ManagerObjectFactory in core. Also talk to Remy, see if there is way to bind to the correct place in Tomcat. -- 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (WELDX-35) Use tomcat plugin to download and run servlet integration tests

by Pete Muir (JIRA)

Use tomcat plugin to download and run servlet integration tests --------------------------------------------------------------- Key: WELDX-35 URL: https://jira.jboss.org/jira/browse/WELDX-35 Project: Weld Extensions Issue Type: Task Components: Servlet Containers Reporter: Pete Muir Fix For: Servlet Containers 1.0.0.CR2 -- 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

13 years, 10 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2010