October 2011 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-645) Analyse bootstrap hotspots

by Pete Muir (JIRA)

Analyse bootstrap hotspots -------------------------- Key: WELD-645 URL: https://jira.jboss.org/browse/WELD-645 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Pete Muir Fix For: 1.1.0.BETA2 -- 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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (WELD-491) Warn if CDI annotations are placed on classes that are not managed beans

by Nicklas Karlsson (JIRA)

Warn if CDI annotations are placed on classes that are not managed beans ------------------------------------------------------------------------ Key: WELD-491 URL: https://jira.jboss.org/jira/browse/WELD-491 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Priority: Minor Fix For: 1.0.2.CR1 Warn if CDI annotations are placed on beans that fail the 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 -- 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, 1 month

4
12
0 / 0

[JBoss JIRA] Created: (WELD-781) Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications

by Sivakumar Thyagarajan (JIRA)

Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications --------------------------------------------------------------------------------------------------------------------------------------------- Key: WELD-781 URL: https://jira.jboss.org/browse/WELD-781 Project: Weld Issue Type: Feature Request Components: Weld SPI Affects Versions: 1.1.0.Beta2 Reporter: Sivakumar Thyagarajan Priority: Minor Provide a mechanism in ResourceLoader for the SPI implementation to use a module classloader for classloading in multiple-module applications. In the current SPI loadClass(String name) is called and the container such as GlassFish, has no choice but to use the TCL or a generic classloader for the application. For applications that have multiple modules(such as an EAR), the container needs a mechanism to identify which module the Class/resource being loaded belongs to, so that it can use the appropriate module classloader. So, for instance, it would be nice if the SPI could be modified to have a public Class<?> classForName(String name, BeanDeploymentArchive originatingBDA); instead of classForName(name) and equivalents for the other methods in ResourceLoader. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (WELD-775) Try to reduce runtime use of heap

by Pete Muir (JIRA)

Try to reduce runtime use of heap --------------------------------- Key: WELD-775 URL: https://jira.jboss.org/browse/WELD-775 Project: Weld Issue Type: Bug Reporter: Pete Muir Currently we hit around 9100 sessions in the QA lab before running out of heap. It's possible that we can improve on this by cleaning up the sessions more aggressively. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
14
0 / 0

[JBoss JIRA] Created: (WELD-694) Move WeldManager to API and split out container integrator methods to another interface

by Pete Muir (JIRA)

Move WeldManager to API and split out container integrator methods to another interface --------------------------------------------------------------------------------------- Key: WELD-694 URL: https://jira.jboss.org/browse/WELD-694 Project: Weld Issue Type: Feature Request Components: Weld SPI Affects Versions: 1.1.0.Beta1 Reporter: Pete Muir Fix For: 1.1.0.Beta2 At the same time, add WeldManager to BeanManagerBean types, and also consider renaming to WeldBeanManager -- 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, 1 month

5
6
0 / 0

[JBoss JIRA] Created: (WELD-718) register Weld Servlet listener in web fragment

by Dan Allen (JIRA)

register Weld Servlet listener in web fragment ---------------------------------------------- Key: WELD-718 URL: https://jira.jboss.org/browse/WELD-718 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Priority: Minor Instead of making the developer add the Weld Servle listener in their web.xml when using weld-servlet, might we consider registering it for them automatically but including it in a web.xml fragment or TLD that's bundled in weld-servlet.jar? The benefit of using the TLD is that it would work in pre-Servlet 3.0 environments. META-INF/web-fragment.xml <web-fragment xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd" version="3.0"> <listener> <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> </listener> </web-fragment> META-INF/weld.tld <taglib xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_0.xsd" version="2.0"> <description> An empty tag library that registers a listener to bootstrap Weld in a Servlet container. </description> <tlib-version>1.0</tlib-version> <short-name>w</short-name> <uri>http://jboss.org/weld</uri>  <listener> <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> </listener> </taglib> Btw, we are already including other automatic configurations, such as a JSF phase listener and view handler (META-INF/faces-config.xml). If we require ordering, that leans more to web-fragment.xml as a solution, since it's possible to have ordering control. There is no guarantee as to when a listener will load that's defined in a TLD (the advantage is only for non-Servlet 3.0 containers). Given that Weld is a new programming model and likely to be used with newer containers, then I'd say we should go with web-fragment.xml. (Worse case scenario is we introduce a classifier for weld-servlet that will be for pre-Servlet 3.0 environments. Something like org.jboss.weld.servlet:weld-servlet:1.1:pre-servlet-3) -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (WELD-668) Support @Resource injection in Weld Servlet

by Pete Muir (JIRA)

Support @Resource injection in Weld Servlet ------------------------------------------- Key: WELD-668 URL: https://jira.jboss.org/browse/WELD-668 Project: Weld Issue Type: Feature Request Components: Servlet Container Support 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (WELD-667) Support @Resource injection in Weld SE

by Pete Muir (JIRA)

Support @Resource injection in Weld SE -------------------------------------- Key: WELD-667 URL: https://jira.jboss.org/browse/WELD-667 Project: Weld Issue Type: Feature Request Components: Java SE Support Reporter: Pete Muir Fix For: 1.1.0.Beta2 -- 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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (WELD-692) Check that BeanDeployment is not being kept around after bootstrap

by Pete Muir (JIRA)

Check that BeanDeployment is not being kept around after bootstrap ------------------------------------------------------------------ Key: WELD-692 URL: https://jira.jboss.org/browse/WELD-692 Project: Weld Issue Type: Sub-task Components: Bootstrap and Metamodel API 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (WELD-867) bean implementations should be serializable

by Gerhard Petracek (JIRA)

bean implementations should be serializable ------------------------------------------- Key: WELD-867 URL: https://issues.jboss.org/browse/WELD-867 Project: Weld Issue Type: Feature Request Components: Built-in beans Affects Versions: 1.1.0.Final Reporter: Gerhard Petracek Priority: Blocker Fix For: 1.2.0.CR1 for custom scope implementations it's required that beans are serializable. -> one of the following classes should implement java.io.Serializable https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/wel... https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/wel... https://github.com/weld/core/blob/master/impl/src/main/java/org/jboss/wel... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues October 2011